This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Sorry if this question is duplicated; I did search the forums but none of the topics I found seemed to represent my scenario. We are building a financial application in .NET Framework 4. Some of the clients that will buy our application will want to use the application with the database in SQL Server 2008+, and others want to use the application with Oracle 10g+. In both cases the database schema for the application is identical (same table names, same column names, as equivalent as possible data types), with the small exception that the identity columns in SQL Server use sequences in Oracle. Some of those columns are primary keys of their respective tables. Ideally, we would like to find an ORM that allows us to simply change the connection string and provider in the configuration file, and using the same mapping the application should be able to run in either SQL Server or Oracle. Is this possible with LightSpeed? If that ideal scenario is not possible with LightSpeed, what would be the minimum-effort scenario where we could switch between the two DBMSs ? In other ORMs we have seen it requires things like maintaining two sets of mapping files (or mapping code), or in some cases keeping two sets of separate assemblies that we need to swap and recompile. This gives us a lot of overhead we would like to avoid if possible. Thanks in advance for the information. |
|
|
|
|
Yes this should be fine with LightSpeed, you can swap the provider type, identity mode and connection string as part of configuration or in code or at runtime by updating those properties on the LightSpeedContext instance you are using. I would suggest you do a quick prototype to verify that this satisfies your requirements, you should be able to spike this out fairly quickly to confirm if there are any other differences when switching providers.
|
|
|
|
