StrataFrame Forum / StrataFrame Application Framework / Business Objects and Data Access (How do I?) / Oracle SQL vs MS-SQL / Latest Posts

RE: Oracle SQL vs MS-SQL

Ben Chase — Wed, 05 Jul 2006 09:11:25 GMT

No problem :)

RE: Oracle SQL vs MS-SQL

Daniel Essin — Mon, 03 Jul 2006 19:34:17 GMT

Thanks.

RE: Oracle SQL vs MS-SQL

Ben Chase — Mon, 03 Jul 2006 09:06:42 GMT

This is the 3rd party product we have researched that will convert the SQL statements from one provider type to another:

http://www.swissql.com/products/sqlone-apidotnet/sqlone-apidotnet.html

RE: Oracle SQL vs MS-SQL

Daniel Essin — Sun, 02 Jul 2006 13:17:23 GMT

What third-party product?

RE: Oracle SQL vs MS-SQL

Trent L. Taylor — Thu, 08 Jun 2006 21:16:08 GMT

There is one option through framework to have a "non-provider" specific query created and this is the same approach we take on the BrowseDialog control. If you'll notice the overloads on the FillDataTable method on any business object, it has an overload with a QueryInformation parameter. This QueryInfo class allows a query to be forumulated that is not provider specific and it is automatically converted by the data access layer. This allows the DAL to swap and the code to remain the same. There are obviously a few restrictions when taking this approach and it is not a solution for a 100% non-provider specific environment, but it will get you a long way down the road.

Generally this is handled on the side of the developer. There have been some developers run all of their queries through a third-party product that allows the "from" and "to" database languages to be specified and it converts on the fly. Others know that they will either be dealing with one or two langauges and program the logic accordingly in the BO.

Hope this helps.

Oracle SQL vs MS-SQL

Andria Jensen — Thu, 08 Jun 2006 18:25:20 GMT

How does SF handle queries with commands that differ between providers such as SUBSTR vs SUBSTRING, etc. Is that something that needs to be handled on the developer side or is there any kind of translation built into the data access layer?