This is a feature we are currently working on and it is already available if you use the Fluent API. So here are some things you need to consider before trying out a multiple database backends scenario:
- You need to have the same database schema created on both servers, Postgresql and MySQL. You can use OpenAccess to create the schema for you if you prefer using the model-first approach.
- The obstacle that needs to be solved in such multiple-backend scenarios is usually the SQL types that are different for the different backends. You need not to use actual SQL types when you define your mapping via Fluent API, but you need to employ the abstract mapping approach which describes the SQL types that you would like to map to, but allows OpenAccess to decide which is the most appropriate in the correct backend. This way, OpenAccess will know that a unicode string should be mapped to an NVARCHAR in SQL Server and to a NVARCHAR2 in Oracle for example.
We are working on allowing such backend-independent type mapping in the Visual Designer as well, which would allow a user to use multiple backends with one .rlinq file, but that is not possible for the moment.
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!