>> query in DODS by calling methods such as >> >> callLogQuery.addWhereClause( callLogTable.State, "NJ", QueryBuilder.EQUALS) >> callLogQuery.addWhereClause( "extention", "1111", QueryBuilder.EQUALS) >> callLogQuery.addWhereClause( "duration", "60", QueryBuilder.GREATER_THAN) > > I have considered making something like this, except with more > pleasant expressions. Maybe something like: > > query = AND(VAR.callLogTable.State == "NJ", VAR.extension == 1111, > VAR.duration > 60)
I have used systems in the past where the query has been completely objectized, it worked but it sucked, and the first thing I did was to circumvent it to be able to add text ala "clauses". Because making a simply query used to take a fortnight. Using objects is great, but sql is great (ish) too. I think using 3 lines, like the example, above to write the one liner (below), which incidentally, reads well... "state = 'NJ' and 'extension' = 1111 and duration > 60" ...is overkill. The tables are "like" objects, so we should treat them so, queries are like more like prose. tom _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
