Thanks guys.
I also fixed the second INSERT.
And made the simple methods to the pref table default.
I want to deprecate the old users table.
On 10/13/05, John Stevens <jst...@gm...> wrote:
> Hi Thomas,
> It was meant to allow for you to configure the INSERT clause for the
> backend DB you use. This was the for Oracle. Since Oracle does not have=
a
> REPLACE clause (MySQL specific), I used this to to do an initial INSERT f=
or
> user prefs. Without it, user prefs were never saved or updated. See my
> Rant ;)
> Regards
>
>
> On 10/13/05, Thomas Harding <tho...@la...> wrote:
> > Hello,
> > I've just updated my cvs repository.
> >
> > In config/config-dist.ini, I see :
> > ; DBAUTH_PREF_INSERT =3D "INSERT INTO pref SET prefs=3D'$pref_blob',
> userid=3D'$userid'"
> >
> > This is not compatible with Postgresql !
> >
> > The good statement for _all_ SQL SGBDRs is :
> > DBAUTH_PREF_INSERT =3D "INSERT INTO pref (prefs,userid) VALUES
> ('$pref_blob','$userid')"
> >
> > While config-dist.ini is used by the configurator, it will be wise to
> > correct this :)
--
Reini Urban
|