Re: Hotfix available for LedgerSMB 1.2.5 error

["Chris Travers" <..hidden..>]

SVN is working for me.  We are likely to move off of Sourceforge in
the near future for svn in part so we can better control commit
priveleges.  But in the mean time, I suggest filing a support request
with the Sourceforge folks.

Best WIshes,
Chris Travers

On 5/19/07, Vladimir Botka <..hidden..> wrote:
> I am not able to checkout the repository. My fault, or the apache
> module crashed?
>
> # svn co
> https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk
> ledger-smb
>
> svn: PROPFIND request failed on '/svnroot/ledger-smb/trunk'
> svn: PROPFIND of '/svnroot/ledger-smb/trunk': could not connect to
> server (https://ledger-smb.svn.sourceforge.net)
>
> -vlado
>
> Dne Fri, 18 May 2007 22:28:52 -0700
> "Chris Travers" <..hidden..> napsal(a):
> > You probably still need to get the new Form.pm.  The problem is not in
> > the data or the database schema but one of the queries that was
> > rewritten in order to get better performance on systems with large
> > databases.
> >
> > If you need me to, I can send it to you.
> >
> > Best Wishes,
> > Chris Travers
> >
> > On 5/18/07, Vladimir Botka <..hidden..> wrote:
> > > Dne Fri, 18 May 2007 12:55:34 -0700
> > > "Chris Travers" <..hidden..> napsal(a):
> > >
> > > > When issuing an AP transaction in 1.2.5 (only), you may get the
> > > > following error:
> > > >
> > > > ERROR: column "customer_id" does not exist
> > > >
> > > > This problem was caused by a problem with one of the performance
> > > > patches which made it into 1.2.5.  A fix has been committed to SVN
> > > > branches/1.2
> > > >
> > > > Anyone experiencing this problem has the following options:
> > > > 1)  Downgrade to 1.2.4 (just requires untarring over the top)
> > > > 2)  Contacting me for an appropriate hotfix (I will send you a
> > > > replacement Form.pm).
> > > > 3)  Download Form.pm from SVN (branches/1.2).
> > > >
> > > > Best Wishes,
> > > > Chris Travers
> > >
> > > I have solved this issue with:
> > >
> > > 1. dump the 1.2.4 dataset
> > > #pg_dump -d -F tar -U pgsql -f dataset.dump dataset.1.2.4
> > > 2. create new dataset.1.2.5 (in admin.pl)
> > > 3. restore the dataset
> > > "#pg_restore -c -U pgsql -d dataset.1.2.5 dataset.dump"
> > >
> > > There was no complains from lSmb 1.2.5 up till now. Is this O.K. ?
> > > -vlado
> > >
> > > --
> > > Dr.Vladimir Botka
> > > ..hidden..
> > >
> > >
> >
>
>
> --
> Dr.Vladimir Botka
> ..hidden..