[freeside] MySQL & Freeside prob?

[Nyamaka Tutsirayi Admore]

Gee, so l guess l have to use postgress as well, l thought the comments on
the LOCK.... said it was harmless, and l was about to use the test onto a
production environment..and get my head cut off by race and duplicate
conditions

Customers( Kings) were goiing to order for my stupid head! when they failed
to login or got somebod'y details!!

Thanks, let me run around!!!

Phew, that was close

Admore____________________Nyamaka
----- Original Message -----
From: "ivan" <ivan at 420.am>
To: <ivan-freeside at sisd.com>
Sent: Wednesday, February 23, 2005 09:02
Subject: Re: [freeside] MySQL & Freeside prob?


> On Thu, Mar 23, 2006 at 08:19:44AM +0200, Nyamaka Tutsirayi Admore wrote:
> > Brother, l am not a good programmer but l came across that error too,
and
> > guess what, that statement is not supported by
> > even MySQL5, but the solution is hacking the code (sorry _ivan)
> >
> > Just comment out that whole section of code that has to do with locking,
if
> > you read the comments abov, you will realise that you are doing no harm
to
> > the functionality,
>
> Hmm, well, you're removing an important part of the protection against
> duplicate usernames (and "username at domain"s, uids) and are open to race
> conditions that could result in duplicates...  I wouldn't personally
> call that "no harm to the functionality" or say that's a viable option
> for a supported MySQL port, unfortunately.
>
> --
> _ivan
>
>
> > ----- Original Message -----
> > From: "ivan" <ivan at 420.am>
> > To: <ivan-freeside at sisd.com>
> > Sent: Wednesday, February 23, 2005 07:53
> > Subject: Re: [freeside] MySQL & Freeside prob?
> >
> >
> > > I'll remove MySQL from the documentation unless there is support from
> > > the community to keep the MySQL port up-to-date.  While I do my best
not
> > > to be overly database-specific, unfortunately I just don't have the
> > > resources to maintain the code against multiple DB backends.  All my
> > > installs are on PostgreSQL.
> > >
> > >
> > > On Tue, Feb 22, 2005 at 08:51:59PM -0500, Brian Taber wrote:
> > > > I would say make you life easy and use Posrgres...  but I am sure
there
> > is
> > > > a way  :)
> > > >
> > > >
> > > > -------------------------
> > > > Brian Taber
> > > > Manager/IT Specialist
> > > > Diverse Computer Group
> > > > Office: 508-758-4402
> > > > Cell: 508-496-9221
> > > > btaber at diversecg.com
> > > >
> > > > >
> > > > >  Hi Folks,
> > > > >
> > > > >  I'm in the process of evaluating FreeSide, and thanks to some
great
> > help
> > > > > on the IRC channel, am most of the way there. However it seems
that
> > some
> > > > > SQL statements are failing.
> > > > >
> > > > >  My environment is:
> > > > >
> > > > >  Debian Testing
> > > > >  kernel 2.4.29
> > > > >  MySQL 4.1.10
> > > > >  FreeSide 1.5.0pre6
> > > > >  Apache-ssl 1.3.33
> > > > >  libapacheASP 2.57
> > > > >
> > > > >  When I try to provision an account (edit/process/svc_acct.cgi)
I'm
> > > > > getting an SQL syntax error:
> > > > >
> > > > >  1.  You have an error in your SQL syntax; check the manual that
> > > > > corresponds to your MySQL server version for the right syntax to
use
> > near
> > > > > 'IN SHARE ROW EXCLUSIVE MODE' at line 1 at
> > > > > /usr/local/share/perl/5.8.4/FS/svc_acct.pm line 854. ,
> > > > > /usr/share/perl5/Apache/ASP.pm line 1518
> > > > >
> > > > >  From the mysql log, this is what it's trying to do: 'LOCK TABLE
> > svc_acct
> > > > > IN SHARE ROW EXCLUSIVE MODE'
> > > > >
> > > > >  I'm running the correct version of MySQL, and InnoDB is enabled
by
> > > > > default with a 10MB datafile.
> > > > >
> > > > >  Sadly I'm not a perl or sql guru, can anyone here suggest a way
> > forward?
> > > > > I don't want to have to switch to Postgresql as I'm not at all
> > familiar
> > > > > with it.
> > > > >
> > > > >  -Thanks Max.
> > > > >
> > > >
> > >
> > > --
> > > _ivan
> > >
> >
> >
>
> --
> _ivan