Just a stab in the dark suggestion. Not fully tested (tried simple noddy
test just now.
How about a pre-insert trigger, which will delete entries in Playlist with
the same key and which have timestamps less than the new row. Than, you
can have a constraint that if the primary key is duplicated,
In my database, I am going to be inserting many rows at a time. There
might be duplicate rows in the database which I would not know the
primary key for. There are several databases on several computers
merging into one database which the first ones only occasionally
contact. The schema so far
2 matches
Mail list logo
