StrataFrame Forum » StrataFrame Application Framework - V1 » Enhancement Requests » WhereStatementTypeOptions Additions

WhereStatementTypeOptions Additions

Joe Paquette — Tue, 01 Aug 2006 15:14:34 GMT

Add support for the following:

Between
Not Equals (!=)
Negation (NOT) for:

Like
In
BeginsWith
EndsWith
Contains

Is Null
Is Not Null

Of course, these additions will need to be supported in the various XxxxDataSourceItem classes.

RE: WhereStatementTypeOptions Additions

Trent L. Taylor — Tue, 01 Aug 2006 15:14:34 GMT

Refer to post 2051.

http://forum.strataframe.net/FindPost2051.aspx

RE: WhereStatementTypeOptions Additions

Joe Paquette — Tue, 01 Aug 2006 15:11:48 GMT

Yes, we must support multiple multiple RDBMS data sources (SQL Server and Oracle).

I understand that the QueryInformation class was originally designed for internal use, but your public API exposes it as an option to hard-coded SQL statements and DBCommand objects. While your documentation correctly recommends using DBCommand objects rather than hard coded SQL statements, even DBCommand requires a SQL statement if a stored procedure is not being used. Best practices suggestes that SQL statements should not be embedded in source code due to differences between RDBMS vendors. The QueryInformation class eliminates this as an issue since it is consumed by the specific DbDataSourceItem implementation. That, in my mind, makes this the preferred approach for FillDataTable() and GetDataTable(). So, to make this as useful as possible, the WhereStatements need to include the missing WhereStatementTypeOptions.

The recommendation was not meant to be a quick fix. The actual coding is no big deal, but you are correct that the testing effort is certainly greater than the coding effort. I was just hoping that this enhancement request would make it in sometime in the not too distant future release.

RE: WhereStatementTypeOptions Additions

StrataFrame Team — Tue, 01 Aug 2006 09:01:07 GMT

Does your application support multiple back-end data sources, or is it targeted towards a specific backend provider?

The QueryInformation class was designed primarily for internal use (so that the business layer can save records and the browse dialog can search for records).

Adding that functionality might take a while to include all of the appropriate unit testing. We will review it at our next staffing meeting, and see if is appropriate to add to the enhancement list.