N
Nick
I've recently been using your LLBL code generator as an assist to
stubbing out my classes and I noticed that you use Sqltypes as your
property return types. If I leave these as is do I have to cast my
values from string toSqlString and from DataTime to SqlDate and from
int to SqlInt32 etc......Isn't that a lot of casting to be doing? I'm
very curious about how to properly use these types. We are developing
a very data intensive web app and any optimization we can get is
beneficial. I'm assuming that if I retrive a string value from a web
control text box, I'm going to have to convert on the way in and on
the way out.
could you elaborate on this for me (or someone) Very intersting, I've
read just about every ado.net book out there and no one does this. Are
they all mising the Boat? Dave, William? what gives guys?
Thanks
Nick
stubbing out my classes and I noticed that you use Sqltypes as your
property return types. If I leave these as is do I have to cast my
values from string toSqlString and from DataTime to SqlDate and from
int to SqlInt32 etc......Isn't that a lot of casting to be doing? I'm
very curious about how to properly use these types. We are developing
a very data intensive web app and any optimization we can get is
beneficial. I'm assuming that if I retrive a string value from a web
control text box, I'm going to have to convert on the way in and on
the way out.
could you elaborate on this for me (or someone) Very intersting, I've
read just about every ado.net book out there and no one does this. Are
they all mising the Boat? Dave, William? what gives guys?
Thanks
Nick