Hi Hilton,
On Thu, Feb 18, 2016 at 8:33 PM, Hilton Day <hilton....@gmail.com> wrote:
> I'm trying to upgrade my old 1.3.46 database (started life as 1.1 from
> memory - back at end of 2006), and have worked my way through a few issues
> so far, like a few duplicate meta numbers, and missing GIFI accounts.
>
Ok. Then you have the hardest part behind you :-)
> Now the upgrade is bombing out with this message:
>
>
>
>
>
>
>
> *Error!Upgrade failed;logs can be found in
> /tmp/ledgersmb/dblog_2016-02-18T191531_2606_stdout and
> /tmp/ledgersmb/dblog_2016-02-18T191531_2606_stderr at
> LedgerSMB/Scripts/setup.pm <http://setup.pm> line 1002.dbversion: 1.4.24,
> company: *
> Looking in the error log (full version of both the stdout and stderr files
> attached), the problems look to me like:
>
>
>
>
>
> *psql:sql/modules/Fixes.sql:164: ERROR: duplicate key value violates
> unique constraint "menu_node_pkey"DETAIL: Key (id)=(90) already
> exists.psql:sql/modules/Fixes.sql:216: ERROR: duplicate key value violates
> unique constraint "menu_node_pkey"DETAIL: Key (id)=(129) already exists.*
>
Errors from Fixes.sql are expected, so these two aren't a problem.
>
>
>
>
> *psql:/tmp/ledgersmb/upgrade.sql:549: ERROR: column "recurring_interval"
> is of type interval but expression is of type textLINE 4: repeat ||
> ' ' || unit as recurring_interval ^HINT: You will need to
> rewrite or cast the expression.*
>
This is your problem. Fortunately, it's probably easy to work around. Try
changing
"""
repeat || ' ' || unit
"""
to
"""
(repeat || ' ' || unit)::interval
"""
That should allow you to get past the current problem. I hope it's the last
one on your route to 1.4! Anyway, I'll change this script for 1.4.26 (We
just released .25 today, but this problem isn't fixed in it).
> The reason I'm trying ot upgrade is having recently picked up my business
> again I'm doing consulting work, and have discovered that I can't post an
> AR invoice any more in my current 1.3.46 - so I figured I'd upgrade to
> 1.4.24 before getting into why (last invoices I posted were a year or so
> ago).
>
That's weird. I'm using companies in both 1.3.46 and 1.4.22, but haven't
heard about this problem before. Let me know if the upgrade fixed things!
> Any help appreciated figuring out this upgrade for now.. I want to get my
> database moved up to 1.4 successfully before I worry about the functional
> issue.
>
>
The advice above should allow you to continue onto the next upgrade steps.
Regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
