I agree with Scott, if your application generate IN condition, could create
CASE too, looks like this
SELECT id, product_id FROM your_table
WHERE product_id IN (6, 3, 4, 10, 7)
ORDER BY
CASE
WHEN product_id = 6 THEN 1
WHEN product_id = 3 THEN 2
On Saturday 04 July 2009 20:44:11 Ransika de Silva wrote:
I have a requirement of storing multilingual words and hence planing to
utilize the Unicode support of the database tables. The question that I
have is, will there be a problem if I make the primary key of a table
multilingual,
Not
Hi,
I am a very happy user of Postgresql! Thank you all for this marvelous work!
I have an older linux server running debian etch 4.0 using the old
postgresql-7.4.
There is essentially a single application running on that machine which serves
up data from a single postgresql database.
There
Michael Gould mgo...@intermodalsoftwaresolutions.net wrote:
1. The ability to encrypt stored procedures and triggers. I know
that PostGres doesn't have this feature but is there a way to
protect stored procedure and trigger source yet allow it to be
executed by any user and how would it
Please keep the list copied. Also, it's best to quote the minimum
required for context, and to avoid top-posting. (It's much easier for
most people to read this way.)
Michael Gould mgo...@intermodalsoftwaresolutions.net wrote:
Kevin Grittner kevin.gritt...@wicourts.gov wrote:
3. We use
I know that by using lowercase object names that I can work with those
object in a case insensitive way, however is there a way through maybe a
locale or character set to make the data and the indexes case insensitive
such that you don't need to use ILIKE?
Best Regards
Michael Gould
Kevin
That sounds like you hadn't yet figured out to set CFLAGS too.
Google or no Google, you're setting the wrong variable.
I had to install PG 8.3.7 on another couple of machines today, and got
exactly the same issue (setting all 3 variables) again on the SPI
module. Please see as
Andy Shellam andy-li...@networkmail.eu writes:
I had to install PG 8.3.7 on another couple of machines today, and got
exactly the same issue (setting all 3 variables) again on the SPI
module. Please see as follows:
FWIW, it does appear that 8.4 makes this better.
FWIW, it does appear that 8.4 makes this better.
OK cheers, I have got plans to migrate over the next month or two; just
wanted to point out the issue.
Andy
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
Hello All -
I
will soon be receiving a new production and warm-standby machine.
Prior to now, we have only had one database machine and no warm
standby.
We had planned to feed the standby with one backup
and then use WAL files rsync'd over until either catastrophe or
maintenance required on
Hello All -
I will soon be receiving a new production and warm-standby machine. Prior to
now, we have only had one database machine and no warm standby.
We had planned to feed the standby with one backup and then use WAL files
rsync'd over until either catastrophe or maintenance required
On Mon, Jul 6, 2009 at 8:38 PM, Jennifer
Spencerjenniferm...@hotmail.com wrote:
Hello All -
I will soon be receiving a new production and warm-standby machine. Prior
to now, we have only had one database machine and no warm standby.
We had planned to feed the standby with one backup and
12 matches
Mail list logo
