On Fri, Mar 24, 2006 at 10:32:42AM -0600, Scott Marlowe wrote: > > > http://bugs.mysql.com/bug.php?id=13301 > > > > > > > from the response: > > > > > Years ago, to help porting applications from other database brands to > > > MySQL, MySQL was made to accept the syntax even though no real > > > constraints were created. > > > i hope postgresql will never "help" me this way. > > No kidding. What bothers me so much about this failure is that there's > not way in the current version to change this behaviour. Everytime > there's a MySQL versus PostgreSQL flamefest on Slashdot or elsewhere, I > see the MySQL folks chiming in with "but the -ansi switch fixes all > those problems" > > It doesn't, and there are many other things I've found that the -ansi > switch doesn't fix. Got a list? I'd love to have it as ammo, and I'm sure that Ian at MySQL Gotchas would love to have it too. > I really really really wish they'd make a version that followed the ANSI > standard more closely, then had a "-compatv4" and "-compatv3" switch to > make it behave like the older MySQL flavors. > > This defaulting to running like an old version, with all its issues is > one thing that makes MySQL so unnattractive to use. That and the fact > that if you've got a problem, the standard answer nowadays is "buy a > support contract". ugh. Happen to have any examples of that as well? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@xxxxxxxxxxxxx Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
