SqlDataSource - Disappointment for professional coders
I was excited about the SqlDataSource control until I tried using it against a stored procedure. It does not throw errors, or indicate in anyway that you have malformed (misnamed, omitted, etc.) parameters. If you pass any parameter type other than Int (Sql int) or String (Sql Varchar), good luck. I wanted to pass in bit (common practice for boolean). No luck. This control appears to be for drag and drop programmers and has
absolutelyno value to people that actually write their own code.
[744 byte] By [
Kentmw] at [2007-12-17]
I agree. Here's the problem I have:
I have two tables (inheritance using a super-class and a sub-class):
(1) Persons
{ id INT PRIMARY KEY AUTO_INCREMENT,
first_name VARCHAR( 50 ),
last_name VARCHAR( 50 ) }
(2) Customers
{ id INT PRIMARY KEY AUTO_INCREMENT,
person_id INT REFERENCES Persons( id ),
customer_type VARCHAR( 50 ) }
Using the ASP.NET 2.0 data binding technologies seems to make this situation much more complicated. Or am I missing something? And I can't seem to use the Databindings property collection on the controls anymore.