After review, run the second transaction in the
sql/upgrade/1.3-1.2.sql and this will clean things up.
Currently we keep the lsmb13fail schema around for troubleshooting
after the fact. I will add a note to it that you have to remove the
schema after you are done looking into it or else you canno
Thanks
~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
Linda Ursin
Heksebua
Adresse: Tlf: (+47) 402 40 767
Solvangwww: http://heksebua.com
7288 Soknedal E-post: li...@heksebua.com
Org: NO 995 5
On Mon, Mar 12, 2012 at 3:24 AM, Linda Ursin wrote:
> No. I did a complete rollback, but I just now managed to fix it by dropping
> the chemas public and lsmb_13fail and renaming lsmb12 to public. I can now
> access the LedgerSMB, and it has content (which the rollback didn't).
Ok. I will send y
No. I did a complete rollback, but I just now managed to fix it by dropping
the chemas public and lsmb_13fail and renaming lsmb12 to public. I can now
access the LedgerSMB, and it has content (which the rollback didn't).
Linda
~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
Are you trying to access via 1.3 or 1.2?
Best Wishes,
Chris Travers
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio,
I tried this:
UPDATE defaults SET value = '1.2.26' WHERE value = '1.3.11';
but it didn't help.
Linda
~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
Linda Ursin
Heksebua
Adresse: Tlf: (+47) 402 40 767
Solvangw
