2006-04-01 (토), 19:26 -0700, Brendan Duddridge 쓰시길:
> Excellent. I've just downloaded citext and I'll try it out. Are there
> any problems with it?
> It seems like this should just be added as a default data type to
> PostgreSQL.
>
> Thanks,
>
> ___
2006-04-01 (토), 21:19 -0500, Robert Treat 쓰시길:
> On Friday 31 March 2006 18:51, chris smith wrote:
> > On 4/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I'm hoping someone can tell me how to go about this, or if a solution is
> > > even possible with my current set up.
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Robert
Treat) transmitted:
> On Thursday 30 March 2006 03:03, Aaron Glenn wrote:
>> Anyone care to share the great books, articles, manifestos, notes,
>> leaflets, etc on data modelling they've come across? Ideally I'd like
>
Excellent. I've just downloaded citext and I'll try it out. Are there
any problems with it?
It seems like this should just be added as a default data type to
PostgreSQL.
Thanks,
Brendan Duddridge | CTO | 403-277-5591 x24 |
On Friday 31 March 2006 18:51, chris smith wrote:
> On 4/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I'm hoping someone can tell me how to go about this, or if a solution is
> > even possible with my current set up. I realize this question may go
> > beyond pure postgres top
On Saturday 01 April 2006 17:26, Brendan Duddridge wrote:
> We used to use FrontBase for our databases, but we have since
> switched to PostgreSQL for
> performance reasons. However, FrontBase did have very nice collation
> support.
>
> To get case insensitive searches (even on UTF-8 data), all you
We used to use FrontBase for our databases, but we have since
switched to PostgreSQL for
performance reasons. However, FrontBase did have very nice collation
support.
To get case insensitive searches (even on UTF-8 data), all you had to
do was alter the column
and set its collation to 'CAS
On March 31, 2006 10:39 pm, Brendan Duddridge <[EMAIL PROTECTED]>
wrote:
> Thanks Tom,
>
> I just didn't know if that was normal or not. I actually saw 4 WAL
> files / minute today. I set checkpoint_segments = 128, so maybe that
> will help.
That's normal, if your database is busy. I get up to 6
Hi Akhilesh,
Can you send the script please I want to see that.
--Nirmalya
--- AKHILESH GUPTA <[EMAIL PROTECTED]> wrote:
> hi all,
> just to ask u all one thing regarding encryption/decryption.
>
> i am migrating my database from mysql to pgSQL using a php script.
> in mysql there is a ta
> A while back, I posted about seeing a number of warnings from pgpool:
>
> http://archives.postgresql.org/pgsql-admin/2005-03/msg00305.php
>
> A typical pair of statements in my postgres logs looks like this:
>
> WARNING: there is no transaction in progress
> STATEMENT: ABORT
>
> Tatsuo Ishi
I hate ILIKE. it's abnormal, as there is no way to forget it and use
standard things (I can hardly wait collation support).
So, every time I type 'ILIKE' I think: I DON'T LIKE ILIKE. In other
words, 'ILIKE' couldn't be true for me and PostgreSQL makes me lie.
--
Best regards,
Nikolay
April, 1st.
On 4/1/06, AKHILESH GUPTA <[EMAIL PROTECTED]> wrote:
> hi all,
> just to ask u all one thing regarding encryption/decryption.
>
> i am migrating my database from mysql to pgSQL using a php script.
> in mysql there is a table 'users' where a field 'password' is there of type
> varchar(30),
> and
hi all,
just to ask u all one thing regarding encryption/decryption.
i am migrating my database from mysql to pgSQL using a php script.
in mysql there is a table 'users' where a field 'password' is there of type varchar(30),
and is encrypted using AES algorithm, and when i check all the records in
13 matches
Mail list logo