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...Additional Data ProvidersAdditional Data Providers
Previous
 
Next
New Post
12/7/2006 6:25 PM
 

Hi everyone,

First, I'd like to comment on what a fantastic job all of the core and project team members do, in maintaining, updating and supporting the DNN framework.

The only real limitation I can see from the core release product is a surprising lack of data providers. I know the Firebird project is well under way, but are there any plans to have a MySQL provider included with the core framework at any stage in the future?

Apart from MSDE and now SQLExpress, MySQL would have to be one of the largest and most supported free databases.  Over teh years, I have had web sites hosted with over 100 hosts, on both linux and windows platforms, and every one I've come across to date includes MySQL databases as part of the hosting package, where the MS SQL is additional.

Please dont get the wrong idea.  I'm all for supporting the MS platform, and think the .NET framework is great.  I use the MS SQL on my companie's web server (running DNN 4.3.7), but I also do a bit of design work for a couple of charities who want the functionality provided by DNN, but can't afford adding MS SQL to their current web hosting arangements.

I think DNN is a product that deserves widespread support from the general web designer / web hosting / web developmet community.  The best way to leverage this would be to take the Firebird project a lot further and add providers to the core for other (perhaps more popular??) databases such as MySQL and Oracle.

I can hear people screaming "You can write your own provider"... this is true, however creating such a beast requires an intimate understanding of not only the data access routines, but the core framework itself.  Someone without this knowledge or programming skill (someone like me!) would either niot be able to create the required code, or would manage to completely break the core DAL.

Logically, to provide maximum support and useability, providers for additional databases ideally should be part of the core distribution.

OK guys, I've had my vent and made my suggestion.  You may shoot at will, but please only use foam bullets!

Steve.

 

 
New Post
12/11/2006 7:47 PM
 

Steve,

I appreciate your thoughts. I also share the same sentiments that you have. I am glad you took the risk to stand up and say something about it. I have wondered what it would take to write my own data provider and shudder to think that I have to add to my already busy life. MySQL is one of four databases I use on a regular basis and is one that I think needs the most attention right now since it is available on both Linux and Windows operating systems. With Microsoft's recently announced participation in the MONO project, DNN will be able to run on Linux - EXCEPT for the database side.

Christopher

 
New Post
12/11/2006 10:53 PM
 
As the Core member responsible for data access issues I have been profoundly frustrated at my inability to deliver any free alternate data providers.

There is an Oracle provider that has has a long history and is well supported. There is also a MySQL provider. Both of these you have to pay for.

The Firebird provider was free but after a year and a half we were unable to make a release because we constantly lost team members. I feel the reason why is it didn't meet the requirements for success:

  • Who Wants it?
  • Who Needs it?
  • Who Likes it?

For example, look at DotNetNuke...

  • Who Wants it? - Who doesn't want a free easy to use and expand Framework.
  • Who Needs it? - Practically every developer who needs to deliver a solution.
  • Who Likes it? - Millions who have used it.

Now look at Firbird...

  • Who Wants it? - Many people wanted a free powerful database.. until they realized that SQL Express worked in many cases and that you can pay as little as $25 a month for the full SQL server
  • Who Needs it? - Here was the key, no one on the team ran DotNetNuke using the Firebird provider.
  • Who Likes it? - After spending months working with Firebird I realized that I really like Microsoft SQL. This alone would have not stopped the project nor my support for it. But, I need to look at myself before pointing fingers at others.

I spent some time using MySQL when I attempted to make a MySQL provider for free. I do like MySQL and I made tutorials showing how to use it with .Net. A week after creating the article I looked on Google and my article was the number one article returned (the Codeproject article - it has since moved down to number three). This tells me that while MySQL is big, it has very small usage with ASP.NET.

I feel that the reason I have been unsuccessful in nurturing free alternate data providers for DotNetNuke is that among the people interested in DotNetNuke there are not enough interested in using a database other than Microsoft SQL Server.

(or Microsoft Access - sorry but with SQL Server Express being free we cannot justify the development resources required to support it. Though we do realize a lot of people out there love Microsoft Access)

With that said, I continue to remain willing and ready to support anyone who wants to create an alternate data provider for DotNetNuke. If you are willing to get the project going I and the Core are ready and willing to do all we can to help you.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
12/12/2006 12:02 AM
 

Thanks for your reply Michael,

Out of all of the literature that is available for the DNN framework, your tutorials are the ones I turn to most in my meek attempts to develop costom modules for my inhouse use.

I understand and appreciate the effort required to create additional components of the DNN core, and my post is not intended to be a criticism of DNN which I think is one of the most well put together offerings available, but to stimulate a discussion amongst the community and hopefully gain enough support for the core team to add a provider for MySQL to the core framework.

Personally, I would be more than happy to assist in the development of this provider, but my skill as a VB programmer leaves a LOT to be desired (my original training as a programmer was on the old IBM system 36, System 38 and AS400 machines, and in COBOL).  The only modern object oriented languages I know I have taught myself from reading official reference materials, and from tutorials such as yours.

I'm sure if I have a use for a MySQL provider there must be others, so if anyone has looked at the DNN framework and passed on it because it only interfaces with MS SQL "out of the box", then please, make a post here and let the core team know that this is something that the community does want, and will use.

It also never hurts to let Michael, Scott, and the other core team members know that we all really do appreciate all the work they put into the DNN project. 

Thanks Guys (and Gals!).

 
New Post
12/12/2006 6:23 PM
 

Michael,

I was not aware of the history associated with the data providers. I cannot fully appreciate the frustration you have in this endeavor because I don't know what it requires. I too have minimal development capability to offer. I run a lot of solutions on LAMP environments and work as a consultant in the construction industry. The construction industry is one of the largest industries in the world and this country. Yet, it runs on a paper thin profit margin. There is a lot of money to be made, and very little left over after the projects blow their budgets.

But, back to the original thought. LAMP environments provide the construction industry with alternatives that are more cost effective and efficient for their needs. LINUX is in the industry to stay and is gaining popularity. So is MySQL. While the demand is small now, and the opportunities are few - I see a lot of potential in this industry for project management solutions using DNN. Recently Microsoft and Novell made a couple announcments of how Microsoft will now contribute and take an active role in developing MONO to leverage ASP.NET on the Linux platform. Microsoft also recognizes that the database of choice on Linux is MySQL with PostGRE folling closely behind.

My brother (a DoD software engineer, WINE developer, and MONO developer) and I discussed the impacts of this decision by Microsoft and what they are doing. The only thing we can agree on is that Microsoft is pulling an "Old Blue" where they are doing what IBM did to redefine themselves. If Microsoft is doing that, then the chances are higher that Microsoft will start porting all of their .NET applications to work with MySQL so they can maintain sales and continuity in their offerings. With that said, it is quite possible that SharePoint could be ported to MySQL when MONO reaches full ASP.NET 2.0 compliance.

Am I off base here? Am I missing something?

I also turn to Michaels tutorials, reviews, and comments more frequently than anyone else. I am just not a regular contributor to forums because gurus like Mr. Washington have gotten all of the answers out in the open before I even had the question. Kudos to you!

Regards,
Christopher Stimpson

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Additional Data ProvidersAdditional Data Providers


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