Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Getting DNN to work with Firebird and/or Advantage Database ServerGetting DNN to work with Firebird and/or Advantage Database Server
Previous
 
Next
New Post
6/16/2008 5:42 AM
 

Hi,

Can anyone tell me what would be involved (code and sql change wise) in getting DNN to work with these 2 databases.

I know that the Firebird project was abandoned. Why was this?

I have just started with a new company who only use Firebird and Advantage Database Server therefore I cannot use MS-SQL at all, not even the express version.

I am willing to take on this project but I need more information as to what is involved.

It would be a shame if I have to abandon using DNN. I have used it for over 3 years now and it would be perfect for my companies web projects.

 

Regards

 

Mie

 
New Post
6/16/2008 6:01 AM
 

Mike,

to make DNN work with another Database requires to write database providers for core framework and all modules you use, which needs a huge effort (and was the reason to abandon the Firebird provider project). AFAIK there is currently only one 3rd party database provider, i.e. Oracle from EquityDP. I suggest to contact Sanjay (who also worked on the firebird project ~2 years ago) for more details.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/22/2008 4:05 AM
 

Sorry for the delay Sebastian.

 

I see what you mean. Even if I did get the core working, I would not be able to use any 3rd party modules without having the source code and updating them.

Looks like I am going to have to abandon DNN, at least until there is a possibility of using other databases e.g. if the core team decide to use Entity frameworks or at least an ORM.

I have invested a lot of time into it.

 

I think that any support of multiple databases must come from the core team as a means to drive 3rd party developers.

 
New Post
7/22/2008 5:13 AM
 

Mike,

as long as 3rd party modules follow the database provider scheme, you do not need sourcecode, only recreate the provider for your database - which is still an enormeous effort, IMHO. Of course, the core team looks into various alternatives, but be aware, that a major change like changing the complete data layer has huge impact and will only be taken, if the benefit clearly dominates the efforts and risks.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/22/2008 3:52 PM
 

I was going to say some of what Sebastian said, properly designed modules shouldn't need any conversion.  Unfortunately, there might be 10% of the modules out there that are designed properly (mine sure aren't...).  I have seen one organization write their own provider several years ago, for DB2, but in the process they ended up rewriting most of DNN anyway.  There's probably no DNN left in their current app.

Future use of LINQ might provide an answer, but by now the DNN core is pretty strongly married to a MSSQL environment.  I converted two older Oracle databases to SQL and one of the reasons was to use DNN (the other was the Oracle guy left...), but that's not an easy solution for many people either.

Jeff

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Getting DNN to work with Firebird and/or Advantage Database ServerGetting DNN to work with Firebird and/or Advantage Database Server


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out