Are there integrity constraints in the underlying database that might be violated by removing these rows?
Are there integrity constraints in the underlying database that might be violated by removing these rows?
Thanks for reply -- I've completely redesigned this since then (thanks to my father-in-law's brilliant communications skills of saying one thing and meaning another), so this thread should be removed...
Turns out, no, there weren't any constraints...I had had them on, but took them off thinking they were the problem...As part of my learning curve with cute, I've come to realize that using the model/view classes can sometimes cause unexpected results so I've gone straight to SQL a few times so that I know exactly how the code is behaving...Coming from a day job of Oracle I feel a lot more comfortable depending on the order of delete/insert/update at that level since I have no easy way of peeking at how the models (and in some cases the mapping) behave...
thanks for the reply, though!
scott
Bookmarks