Excellent! Thanks for providing both the idea and an example. I didn't get the
idea right away, but the example made it clear. I'll try that on my table and
report back on how it works out.
Regards,
-Nick
--
Nick Fankhauser
On Sun, May 08, 2005 at 01:55:56PM -0500, Nick Fankhauser wrote:
>
> Hi- I'm doing a conversion from an older database in which a memo field was
> handled by storing one line per record and then displaying the related
> records in order. I want to compress all of the lines into a single text
>
Hi- I'm doing a conversion from an older database in which a memo field was
handled by storing one line per record and then displaying the related records
in order. I want to compress all of the lines into a single text field with one
record per memo entry.
So for instance, the old database look
Ain't trying to prove no one no thing.
So sorry.
Thamks.
On Sunday 08 May 2005 19:43, you wrote:
> Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> writes:
> >> If you're still using a PostgreSQL version that has the --enable-locale
> >> option then you rather need to upgrade.
> >
> > And
A few weeks ago I posted a way to do efficient range predicate joins,
given only B-tree indexes. I've since gotten back home and looked at the
code I last used. My apologies for an offhand hasty posting.
The following is the solution I worked out when I used this method on a
large data conversion.
Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <[EMAIL PROTECTED]> writes:
>> If you're still using a PostgreSQL version that has the --enable-locale
>> option then you rather need to upgrade.
> And excuse me ?
> [EMAIL PROTECTED] postgresql-8.0.2]# ./configure --enable-locale
> checking build system type...
Hi,
And excuse me ?
[EMAIL PROTECTED] postgresql-8.0.2]# ./configure --enable-locale
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking which template to use... linux
checking whether to build with 64-bit integer date/time support...
BR,
Aarn
