Hi,

Yes, you did ask it before and my answer is stil the same.

http://www.mojoportal.com/Forums/Thread.aspx?thread=1788&mid=34&pageid=5&ItemID=9

Best,

Joe 

Implementing support for a new database is a lot of work and maintaining it is a lot of work. If the syntax is similar to one of the other dbs you might be able to do a lot of copy/paste and find and replace to do the initial implementation assuming it has similar ADO.NET providers and helpers.

Might I ask why you are so eager to use this db, what is the big advantage?

I know of someone in the community who said he was going to try and implement support for VistaDB not sure if he has made progress or given up, I haven't heard from him in a while. It seems more compelling in terms of a file based embeddable db because it is all managed .NET code and can run in medium trust environments from what U inderstand.

Best,

Joe

People often assert that  using NHibernate means you support lots of dbs but when you start actually supporting more dbs you find that the schemas are not identical across systems because data types are not always identical (ie native Guid vs char(36)) so the mapping files needed for different db platforms under NHibernate will not always be the same across db platforms.

If you like N2 and it can really support your db then you should use it. N2 as far as I see only supports MS SQL and MySql, I don't accept the premise that it supports lots of dbs just because it uses NHibernate. If I see people actually using it and it working correctly on more db platforms without platform specific bugs then I will believe it. The problem is you do run up against platform specific issues and using NHibernate you hit a brick wall until they fix it (unless you understand its deep internals and can fix it yourself) whereas using traditional non-OR Mapper approaches its easier to fix it yourself.

No project that I know of actually supports more dbs than mojoPortal. We support 5 db platforms and they really work.

Best,

Joe