From: | "John Huttley" <john(at)mwk(dot)co(dot)nz> |
---|---|
To: | "Dustin Sallings" <dustin(at)spy(dot)net> |
Cc: | "pgsql-general" <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] Limitation |
Date: | 1999-06-24 22:04:35 |
Message-ID: | 00b001bebe8d$8ce16340$1401a8c0@Mr_Creosote.MWK.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Your idea could not be made to work in the actual
environment.
Everyone is ignoring the point of this.
PG doesn't do something(s) that a second-rate
commercial db can. And it does it very nicely.
Thats the point.
I'm looking for a hacker to say 'Thats interesting,
I'll have a look at sometime.'
Anybody interested?
Regards
> Honestly, I think it's the same reason someone would want to
>insert data as a single string, then create a view that does substrings to
>produce the appearance of a multi-column table (which, I assume is then
>selected on from certain fields, causing table scans). Sometimes, people
>try to wedge efficiency into an inefficient design, which rarely works.
>My approach here would be to substr before insertion, then make a view to
>concatenate the results.
>
>--
>SA, beyond.com My girlfriend asked me which one I like better.
>pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin(at)spy(dot)net>
>| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
>L_______________________ I hope the answer won't upset her. ____________
>
From | Date | Subject | |
---|---|---|---|
Next Message | Artur Pietruk | 1999-06-24 22:20:09 | Re: [GENERAL] Problems building pgsql 6.5/6.4 on AIX gcc |
Previous Message | John Huttley | 1999-06-24 21:53:37 | Re: [GENERAL] Limitation |