Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

TeeJay
  (email not shown publicly)
http://www.aarontrevena.co.uk/

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN : TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl [livejournal.com]
flickr :hashbangperl [flickr.com]

Journal of TeeJay (2309)

Friday June 27, 2003
09:11 AM

annoying bug in oracle

[ #13098 ]
I have a table I am inserting records into - it has a unique constraint on a composite primary key - if the constraint is broken - it still inserts the record *with* the primary key but loses the values of some of the other columns.

This is bad

Either don't insert the record - or insert all of it don't just plonk random data in the record and moan about constraints being broken you useless lame excuse for a database.

Don't get me started on being limited to 30 char identifiers and complaining about them being too long without even checking to see if it exists

Or the lack of a nice top N results (t-sql) or OFFSET/LIMIT (mysql) - instead having to have deeply nested selects with rowid selected out of each because rownum is calculated before any sorting is done.

When people go on about how MySQL isn't a proper database I think - hang on most of the 'proper' database I have used have far worse problems than MySQL.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.