String lengths in the SQL backend

[Paul Schwartz]

--- On Thu, 11/13/08, Derek Atkins <warlord at MIT.EDU> wrote:

> From: Derek Atkins <warlord at MIT.EDU>
> Subject: Re: String lengths in the SQL backend
> To: pmjs1115 at yahoo.com
> Cc: "Gnucash list" <gnucash-devel at lists.gnucash.org>, gnucash-user at lists.gnucash.org, "Phil Longstaff" <plongstaff at rogers.com>
> Date: Thursday, November 13, 2008, 8:11 AM
> Paul Schwartz <pmjs1115 at yahoo.com> writes:
> 
> > I've worked with several accounting packages, and
> I would find it
> > very strange if someone could not adapt their
> procedures to live
> > with 32 for the length of the account code.
> 
> Except that the UI makes no limitation on the field size...
> So people who convert over could lose data.
> 
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> 
> -derek
> 

True. Introduction of this "feature" should come with sufficient warnings so that the user could adjust his account tree appropriately for this one time event.

Is anything ever perfect?

Paul