Database independent build

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
12/8/2009 6:39:35 PM
Gravatar
Total Posts 1

Database independent build

I am a new comer here and I have some development background.  I was watching the video regarding source code introductions and have a question on the database layer.  I just wonder if it is possible to replace the reference to a particular database type using defined interface and any plans on doing it?   This may release the burden of creating multi-combination of releases and since the data access layer is govern by interfaces, the code is guaranteed to run even adding more database types.  Maybe this is a stupid question and people have asked before.

12/9/2009 6:22:08 AM
Gravatar
Total Posts 18439

Re: Database independent build

Hi,

No, there are no plans to change the structure of data access. There are other projects out there that use OR Mappers if that is important to you, I have my reasons for not using an OR Mapper in mojoPortal.

http://www.mojoportal.com/why-i-dont-use-an-or-mapper-in-mojoportal.aspx

The data layer is an evolving API. Interfaces are not supposed to change, it would be cumbersome to keep creating new versions of an interface for every new or changed data access method.

Most people developing with mojoPortal are only using a single specific database. If there is a "burden" to maintain different data layers and build packages that burden belongs to me.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.