Quote:
Originally Posted by Todd_Clarke
I cut and pasted some of their marketing material below:
|
Gee, thanks.
So, looking at
custom queries.
Code:
// Build the where clause based on column name for the searched
// attribute along with the specified zip codes.
string whereClause = string.Format("{0} in {1}",
Customer._DBSchema[(int)Customer.Attributes.PostalCode].Name,
string.Join(",", zipCodes));
/* Note:
* The where clause could be written this way for better readability.
* However, this is less dynamic then the approach above as it relates
* directly to the column name versus the attribute.
* string whereClause = string.Format("PostalCode in {0}",
* string.Join(",", zipCodes)); */
// Perform the load for the specified where clause
modObjectList.LoadWhere(whereClause);
Okay, so, in this example, I'm actually building the where clause entirely by hand. Basically, the moment I step outside the little box of "really easy" I wind up generating my own SQL.
Yes, it is possible for a sql generator to assist the programmer in generating complex custom SQL, prevent against SQL injection, and do it without mucking about with strings.
I mean, with Modrocko's it looks like mapping a class to a table is really easy. But when that inevitably doesn't work very well, you force the person to fall back to regular SQL.
I'm not a big fan of ORMs to begin with, but I'm baffled as to how it is worth $130 to have something write the most basic SQL code, and then get in the way of writing slightly more complex queries.
I've seen standard database drivers that do more than your product. For $130, I'd hope I could do
custom DDL or import an entire database schema, and handle
inheritance hierarchies. You know, actually have control over my database.
Maybe in version 2.0?
dBforums
>
modrocko
01-07-10, 22:33
Linear Mode
