I decided to upgrade the PostgreSql provider to 2.0.2. today.

It now supports ForeignKey Constraints(relationships), & Functions(stored procedures).

So now it supports:

Generating of Tables/Views/SPs w/ Relationship Support.
 

No extensive testing has been done and I could probably use some help with that and other things.  For example, what is the purpose of the ScriptData methods? I could probably look into it but I'm pretty lazy.

If you just want to test it out/play around with it feel free.  Here's some links for you:

http://langlearn.net/

A build of SubSonic with dependencies(Npgsql, Mono.Security) & the patch are zip up for you here:

http://langlearn.net/PostgreSql%20Provider.zip

Anyway, if I could get an email from a developer or two and be kept in the loop for releases I'd appreciate it.

Thanks,

Justin
 

 I have written a Provider for SQL 2005 Compact edition and am currently building a provider for SQLite. I was wondering if you would like to join me in an Extended provider project where we could put all these providers in a seperate dll while still staying in line with the current SubSonic code base

 I wouldn't mind doing that though I'm sure you've noticed provider encapsulation doesn't really exist right now.  So we'd have to maintain our own build of SubSonic which I would prefer not to do for a couple reasons.  1.  I don't want to step on the original developers toes & 2. I'm fairly new to programming and would prefer to be held to the current developers quality standards for getting my code into a release build.  I don't know if that makes any sense but there you have it.
 

 The new 2.0.2 version of SubSonic just works with my drivers. I had no need to edit the codebase in anyway. I just dropped in my drivers and they compiled and worked as expected.

The encapsulation (or lack of) issue seems to be almost gone in 2.0.2. Only a few lines in Constants.cs currently prevents the PostgreSqlProvider from being a standalone file. These last bits being solved and we could mantain the provider independently of the main project, which I think is even better than having every provider being incorporated into the main codebase.

I'd love to hear from the team, is this going to happen? Are you going in that direction?

 

Sounds great if we can!

I fixed an ORDER BY bug last night.  I'll upload it when I get a chance, although it doesn't seem to be perfect yet.

I believe an effort like this would take some of the strain of the core team's shoulders. At the rate I'm going after the sqlite provider it seems a VistaDB provider is on the cards. My Clients just love the way we can produce results so much faster now. 

maumac:

The encapsulation (or lack of) issue seems to be almost gone in 2.0.2. Only a few lines in Constants.cs currently prevents the PostgreSqlProvider from being a standalone file.

Only Constants.cs?  I was just trying to create a new provider by deriving from DataProvider class and it gave me whole bunch of issues, some of which are abstract members declared internal.  There is no way I can override those and stay out of the codebase at the same time.

On another note, the reason I needed to create a new provider was to create support for tables that do not have primary keys defined.  I know the mantra about convention over configuration, etc., but that alone is already too limiting in my opinion, working with an existing schema which I have no control of.  Of course, you could say, don't use SubSonic and yes, I could use NHibernate among others but SubSonic is so simple to get going, it's almost a shame not using it.  If DataSet can infer primary keys, why can't SubSonic? :)

Ok, I just updated the PostgreSql Provider again.  Any patches I've submitted are obsolete and can be deleted.  I'm just going to leave the patch & build on my host so anyone can grab it that wants it.

UPDATES:

All controls have been patched to work with PostgreSql provider.  To do this I just called the provider.DelimitDbName(table/column) in all queries within the controls.  This must be done because Postgresql lowercases all table/column names if they are not within double quotes.

QuickTables paging/sorting seems to work as well as the SqlProvider's but still seems buggy.  Whoever is maintaining quick tables please shoot me an email, I'd certainly be willing to help out with such a cool control.  If I don't get an email in a couple days I'll probably do it myself anyway.  It's probably a known issue but if you page and then sort(or sort and then page) it doesn't seem to turn up the correct results for that specific page.

Anyway, the code/build can be gotten from the links in the original post. 

Thanks,

Justin 

 I decided to go ahead and fix the paging/sorting in the QuickTable.  There is a patch up on the host just for the QuickTable and a build with it included.  People using other providers may be interested also, I know it works with the SqlProvider.

Actually as I wrote those lines Justin had to patch another couple of files to a new release, including DataProvider itself! I was really being too optimistic...

 

ManyToMany support added.  Only things left seem to be ScriptSchema, ScriptData, & ExtendedProperties. The .zip file in the top post contains a build/patch.

I also added a patch to the DropDown control.  This moves the initialization of the control from OnInit() to CreateChildControls().  The purpose is to allow editing/inserting of properties on Page_Init and Page_Onload.  For example the WhereColumn & WhereValue.

The PostgreSql.patch is all of my code changes combined.