Skip site navigation (1) Skip section navigation (2)

Re: Pet Peeves?

From: Jason Long <mailing(dot)list(at)supernovasoftware(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Pet Peeves?
Date: 2009-01-29 17:04:17
Message-ID: 4981E191.4050501@supernovasoftware.com (view raw or flat)
Thread:
Lists: pgsql-general
Richard Huxton wrote:
> Gregory Stark wrote:
>   
>> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
>> FOSDEM 2009 this year.
>>     
>
> Hmm - three "niggles" things leap to mind.
>
> 1. Case-folding on column-names.
> Quoting is a PITA sometimes when you're transferring from a different
> DBMS. Be nice to have a "true_case_insensitive=on" flag.
>   
I was just wishing for this the other day.
> 2. Non-deferred unique checks
> Merging two sets of data and renumbering pkeys is more fiddly than it
> needs to be. Doesn't happen often, but it's one of the few things we
> don't do "properly".
>
> 3. Date handling
> Sometimes I've got data with invalid dates and it would be great if it
> could replace all the bad ones with, say "0000-00-00".
>
>
> You could throw in non-updateable views, exact-match tsearch queries,
> per-statement triggers not having the old/new rowsets but that's more
> things PG doesn't do rather than things it does.
>
>   

In response to

Responses

pgsql-general by date

Next:From: Tom LaneDate: 2009-01-29 17:05:19
Subject: Re: Text search segmentation fault
Previous:From: Gerhard WiesingerDate: 2009-01-29 17:01:52
Subject: Re: Full backup - pg_dumpall sufficient?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group