On Thursday 05 May 2005 15:01, Bryan Stevenson wrote: > Yeah...but if apply the NOT NULL rrule after...it still shouldn't let you > if there are NULLs in the data ;-);-) (not that this is the case > here...straight import from live DB to local MySQL.....and off to MS SQL)
I don't see how it's possible, though it obviously is. Looking back in my own work journal here, I see that I encountered the exact same problem once myself; the source table contained null values in a field which had a not-null constraint, as well as text data in a numeric-only field, and non-boolean values in a boolean-only field. In my case, however, the target database was Oracle and the source database was... MS SQL. Could it be that there is no such thing as a perfect database? Nah. -- Richard S. Crawford Programmer III UC Davis Extension Distance Education Group 2901 K Street Sacramento, CA 95816 (916)327-7793 http://unexdlc.ucdavis.edu ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205781 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
