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
|
So, I am making an application that gathers and analyzes spectral data and stores it to a database. I am designing the application so that a customer can use it with their RDBMS. I realize that all RDBMS are different and require different ways of connecting. So, I have chosen Lightspeed ORM that handles most of the differences between some common management systems. I am assuming that in lightspeed all i have to do is set the type of DMS and build a custom string using the user credientials provided by the user. Once these are set, lightspeed can take of the rest. I am hearing that it is not that easy. I am wondering what things I should keep in mind when trying to make this software work with multiple databases at runtime and using lightspeed. Example: At a high level I expect the user to go to an options dialog. Pick a RDBMS from the list of providers in Lightspeed. The program will then repopulate a section of custom user credentials specific to the RBMS. The user can then input the credentials. Then, under the hood the program will use these credentials to build a custom string. From there the context provider and connection string will be assigned and ready to go. I would like to know how doable this is using lightspeed and what important concepts must I consider? |
|
|
|
|
Yes this is fine provided you don't need to leverage any DB specific features - e.g. use of stored procs where they are not universally available across all platforms or custom SQL where the syntax max vary across platforms. So if you are strictly using Entities and standard queries this should perform as you expect and the only variance to target each platform would be the connection string.
|
|
|
|
|
Thanks for the reply. Would you mind touching on some RDBMS-specific methods for building strings. I am trying to figure out controls I need to put in the options menu for each database that the user chooses. Maybe could you point me to some good documentation I could look at. Corey |
|
|
|
|
http://www.connectionstrings.com/ has details of the various connection string syntaxs for each underlying ADO.NET provider - Im assuming this is what you are after?
|
|
|
|
