The fix has been partially checked in to the 2.1 branch. The fix has
not been applied to the Group, Role, and Permission tables, but it
appears so far the only problem was occuring in TurbineUser, so that is
what was fixed. Postgres is supported by developers that use postgres.
I try to help incorporate patches needed, but I do not have it set up,
so I only take fixes suggested by users and test that they do not seem
to break anything. It would be great to have a committer who wants to
keep postgres support from lagging. Start supplying patches.
john mcnally
turbine dev wrote:
>
> Hi there,
>
> I have just downloaded and tested v3.0a3 and found
> that the Postgresql problem is no longer affecting the
> sample app. The problem is, we want to stay in v2.1
> for stability (and this is what the Turbine Team have
> recommend). Is there a patch I can download or a
> branch in the CVS that I can get hold of, which has
> the Postgresql problem corrected? I believe there is a
> rather high number of people have been waiting for
> this, because I have been following this issue for
> some time now. From v3.0a3, I can tell the problem
> should have been fixed.
>
> Please consider a "Postgresql maintanence release" for
> v2.1, or please give full instructions on how to
> obtain it through the CVS.
>
> After all, from what I have read in the documents so
> far, Turbine is meant to be db platform independent
> (correct me if I am wrong). Whether or not Turbine
> works with Postgresql is an very important issue IMHO.
> Consider Postgresql is a more advanced RDBMS than
> MySQL, the use of Pg in a more complex environment is
> very important. Is there any reason why the Team have
> been kinda neglected the Pg crowd?
>
> Thanks for your attention.
>
> Sincerely,
> Kenny
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
