On Sun, Jun 27, 2010 at 1:26 PM, Stephen Russell <[email protected]> wrote: > On Sun, Jun 27, 2010 at 4:01 AM, Paul Hill <[email protected]> wrote: >> On Sun, Jun 27, 2010 at 8:44 AM, Grigore Dolghin <[email protected]> wrote: >>> Um.... I don't know about the vb & c# 2008, but 2010 version have the date >>> datatype: >>> >>> Dim x As Date = #10/5/2003# >> >> If I understand correctly Date in vb.net is the same as DateTime in c#. >> So VB & c# do not have a datatype that matches SQLs date type exactly. >> >> It's just something to be aware of. For example, when writing back to >> the SQL database you may need to strip the time out. > ------------------------ > > WTF? > > DateTime invDate = DateTime.Now; > > using(OrderEntity OE = new OrderEntity()) > { > Invocies inv = new Invoices(); > inv.InvDate = invDate; // Answer to the Q why allow case ???? > // other table crap here > > OE.AddToInvoices(inv); // place in queue > int savedCount = OE.SaveChanges(); // process queue now
But in this case SaveChanges() needs to handle the fact that InvDate contains a time element that we need to discard. This could make the code in OrderEntity non-generic when dealing with DateTime types. See what I mean? -- Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
