Thank you for your interest in OpenAccess ORM.
Here is some information regarding the three key points that you are interested in:
1) As far as the connection string is concerned, it is configurable exactly as if you are using ADO.NET for data access - you can have it in code, handled by custom logic, or in configuration files, so that it can be setup by your installation. Furthermore, the backend settings of your data context are now fully configurable through the application configuration file, so that you can additionally make changes when required.
2) You can use windows authentication for connecting to the database, or you can encrypt your connection strings so that the passwords are not visible in the configuration file. One detail in case you choose to use our Visual Designer, rather than the code only approach, is that the connection string is currently stored by default in your .rlinq file for clarity. However, before deploying, you can remove this connection string from the rlinq file (which is in XML format, so you can easily change it), without causing any issues.
3) OpenAccess ORM contains a mechanism of applying schema changes automatically during runtime, based on the current metadata defined either through Visual Designer or Fluent Mapping. However, not everything is supported:
- we are not dropping any objects, or renaming them. You can only change types and add new tables or columns.
- lookup tables creation is not automated - this is something you will have to write code for.
I hope that information helps you in evaluating the product. In addition, you can refer to the overview of all the key features that we are offering and post in our forums any feedback or questions you might have.
the Telerik team
Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!