On Tue, Jun 5, 2012 at 10:49 AM, Robert James Clay <j...@rocasa.us> wrote: > On Mon, 2012-06-04 at 15:14 -0400, Robert James Clay wrote: >> On Sun, 2012-06-03 at 19:59 -0400, Chris Travers wrote: >> > I was looking into this. It looks like Erik committed a fix for this >> > issue for 1.3.16. >> >> .... However, the resulting database does not have the company data that >> should have been brought over from the old v1.2 database, so that aspect >> of the issue is still present. > > Part of that turned to be an database import issue but I was able to > fix that. The issue I'm seeing now on the test db is that the > conversion is failing with the following error (1.3.17 install: > from /tmp/ledgersmb/dblog_stderr): > > psql:/tmp/ledgersmb/1.2-1.3-upgrade.sql:356: ERROR: new row for > relation "entity" violates check constraint "entity_name_check"
This probably happens if there is a customer or vendor which doesn't have a valid name (i.e., at least one alphanumeric character in the name). We might want to add another pre-upgrade check for that. Best Wishes, Chris Travers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Ledger-smb-users mailing list Ledger-smb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
