Hello,

Regardless, the main issue is native IO with unique constraints.

I'm confused. Are you saying (going back to your original example) that SQL will let you set the 2nd record to 30 while the 3rd record is already 30?!

I wouldn't think so!

Therefore, I'm looking at this saying to myself that it's not a question of Native I/O with constraints. It's a question of having a constraint that makes sense for your business rules. (And you don't seem to have that.)

Or does SQL really allow you to ignore the constraint?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.