[Pkg-sql-ledger-discussion] Bug#675816: Name constraint issues upgrading 1.2 db to 1.3 db

[Robert James Clay]

On Mon, 2012-06-11 at 11:22 -0400, Robert James Clay wrote:
> On Sat, 2012-06-09 at 09:48 -0400, Robert James Clay wrote:
> > On Wed, 2012-06-06 at 10:47 -0400, Robert James Clay wrote:
> > > psql:/tmp/ledgersmb/1.2-1.3-upgrade.sql:356: ERROR:  new row for
> > > relation "entity" violates check constraint "entity_name_check"
> > > 
> > >    Quoting one of the authors about it (in a message he posted to the
> > > LedgerSMB user list): "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)."
> 
>   Constraints on some table field values have been tightened up with
> v1.3 of the LedgerSMB database and there appears to still be issues with
> that in the conversion process for at least vendor or customer names.
> More investigation is needed for what kind of name issues it is not
> handling well.

   Besides checking the vendor and customer names in the v1.2 database
being converted, the first & last name fields in the employee table
should also be checked. Besides any issues with the characters being
used (alphanumeric), they also need to actually have some kind of entry
for both fields.




Jame