You could use stored procedures.
I'm starting to port statements originally written for SQL Server over
to Access (with the .Net version of iBatis) and I think I can get away
with defining database specific functions in the properties file that I
define my database information:
Brian,
I think you would be best served by creating separate maps for each
database system. I went from Oracle to SQL Server and found it hard to
impossible to make the sql identical. Using separate maps also gives you
the ability to tune sql statements for the targeted RDBMS. Hopefully you
can
We have a web app that runs against SQL Server. All of our SQL maps are SQL
Server compliant. We now have to be able to support Oracle as well. (We
never thought it would happen... a mistake.)
Anyway, we are wondering if anyone has some general guidelines for writing
SQL Maps so that they run agai
3 matches
Mail list logo
