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...DNN and MysqlDNN and Mysql
Previous
 
Next
New Post
10/10/2007 9:47 PM
 

I know the current DNN version is only designed to work with MS SQL, but I think it would be great to have a choice to use MySql.  Is there any easy way to do this?  Maybe using LINQ?

 
New Post
10/11/2007 4:38 AM
 

sure there is a way, you need to create a dataprovider for the core framework and each module you use - it is not difficult, but time consuming, a team, that wanted to create a firebird provider gave up after a year of work. with availability of free MS SQL Express, the demand has decreased a lot.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/11/2007 10:05 AM
 

I thought there may be some way to abstract the access to the db.  In other words some abstraction layer that should be written into future versions of DNN that would allow all of the modules and core to call a DNN API.  Then the Data providers could be written against that abstraction layer. Obviously this is a big architectural change that would need to be done to the application but seems like a good idea for a "framework". 

leupold wrote

sure there is a way, you need to create a dataprovider for the core framework and each module you use - it is not difficult, but time consuming, a team, that wanted to create a firebird provider gave up after a year of work. with availability of free MS SQL Express, the demand has decreased a lot.

 
New Post
10/12/2007 10:28 AM
 

This is already there, you can simply swap out the provider, there are just 2 big issues.

1.) All tables, stored procedures, views, etc must be recreated against another DB
2.) All modules must also be updated to use the different providers SQL Syntax and connection.

It is available and do-able but it is not a snap your fingers and it is done type of thing, and personally it can't be...


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
10/12/2007 12:10 PM
 

It still sounds like it is not abstracted enough.  Just imagine how Windows abstracts the Win32 API from the hardware.  The Win 32 api stays the same whether you have an Nvidia or ATI, Western Digital or Seagate, etc.  You call higher level functions and the rewiring is done down below.  This is what I am talking about for DNN.  There would be a higher level API and it would be a checkbox to select which data base you want.  This is not that important for me but not everyone wants MS SQL or MS SQL Xpress.  In my opinion rewriting every module to a new provider is not acceptable and just means that the modules should be abstracted more from the database.

mitchel.sellers@gmail.com wrote

This is already there, you can simply swap out the provider, there are just 2 big issues.

1.) All tables, stored procedures, views, etc must be recreated against another DB
2.) All modules must also be updated to use the different providers SQL Syntax and connection.

It is available and do-able but it is not a snap your fingers and it is done type of thing, and personally it can't be...

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN and MysqlDNN and Mysql


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