On Sat, Oct 08, 2005 at 12:49:58PM +0100, test_autoincrement wrote: > This is not user-friendly, and I think the SQL committee made a big mistake > in defining totally different structures for the INSERT and UPDATE > statements. Matter of opinion.
> MySQL already offers this option, so why can't you? MySQL also thinks it's OK to truncate data. Comparing PostgreSQL to them isn't a very good way to go about getting a feature added. Ultimately, I highly doubt that anyone on -hackers has any interest in this, so it's very unlikely to get done unless you do it yourself (or pay someone to do it). Even then I suspect -hackers might reject it. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
