Yep, that's when it's good.rapid development of simple applications
The fake key thing isn't so bad if you use sprocs because you just return the idenity value but I know what you mean, you still need to code around it in some way shape or form.
I'm personally not a big fan of datasets that contain more than one table. There'll be folks ready to shoot me for that because I'm giving up alot of the power they offer but I just find that they're harder to deal with conceptually than a single table result set (or whatever MS choose to call it in it's current iteration)
I must admit, I haven't tried out Linq yet. I guess I pride myself on my ability to write and optimise SQL and I don't trust an abstracted layer to do that optimisation for me. Realistically it probably does a perfectly good job so I'm probably not being rational on that one but old habits die hard. Besides, it's got shifty eyes and it's looking at me funny.
As for inheriting to override functionality, you can but I wouldn't want to and, if you have to, it kinda proves your point that the default functionality isn't meeting your needs.
I used to use JQuery back in the J2 days. Back then it pretty much consisted of a connection object you could chuck a query down. I'm guessing it's expanded since then.
Reply With Quote
