On Mon, 2010-02-01 at 05:31 -0800, Matt wrote: > Not in all cases. For example, I have an invoice with invoice items. > Later on, I edit the invoice and remove some items (but not the > invoice itself). To remove them, I would set item.Invoice=null and > they should be removed from the database if DeleteOnNull is set. What > I get instead is an exception telling me that the foreign key cannot > be null....
Sounds like a bug then. Can you file a bug? Even better, is it possible to create this scenario with the Northwind dataset. If so, a test case written against it will make future testing and integration significantly easier... Thanks, - Jon -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=en.
