We are working on refactoring the codebase.
In 1.0.x and 1.1.x they are in the sql/ directory.
Because 1.2.x was to be the last upgrade with the current structure,
all the Pg-upgrade files were moved to sql/legacy/.
In 1.3.0 and higher, new upgrade scripts are likely to be somewhere
like sql/upg
On Thu, 2007-04-26 at 17:48 -0700, Chris Travers wrote:
> On 4/26/07, David Tangye <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-04-26 at 16:30 -0500, M Lubratt wrote:
> > > Except I manually executed the following from inside psql:
> > >
> > > # \i Pg-upgrade-2.6.12-2.6.17.sql
> > > # \i Pg-upgrade-
On 4/26/07, David Tangye <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-04-26 at 16:30 -0500, M Lubratt wrote:
> > Except I manually executed the following from inside psql:
> >
> > # \i Pg-upgrade-2.6.12-2.6.17.sql
> > # \i Pg-upgrade-2.6.17-2.6.18.sql
> Where did these files coma from. They is NO data
On Thu, 2007-04-26 at 16:30 -0500, M Lubratt wrote:
> Except I manually executed the following from inside psql:
>
> # \i Pg-upgrade-2.6.12-2.6.17.sql
> # \i Pg-upgrade-2.6.17-2.6.18.sql
Where did these files coma from. They is NO database upgrade at 2.6.17
and 18!! ... not even right thru to 2.6
Chris,
The schema version (if that's what you're interested in) was 2.6.12. I
ended up restoring my backup, then following the advice given by "The
Anacrat" (from another thread) outlined in:
http://wiki.koumbit.net/LedgerSmbTransfer
Except I manually executed the following from inside psql:
Take a look at something:
In psql:
select version from defaults;
Best wishes,
Chris Travers
On 4/26/07, M Lubratt <[EMAIL PROTECTED]> wrote:
> Well, I'm finally taking the plunge (on one installation at least).
>
> I've followed the Wiki instructions for migrating a SL installation to LS
> 1.1.
Well, I'm finally taking the plunge (on one installation at least).
I've followed the Wiki instructions for migrating a SL installation to LS
1.1.12. I've encountered a couple of issues and I'm wondering if someone
can point me in the right direction.
1. My cookies don't seem to be working (us