[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Any objections to including the database schema unique id patch?
- Subject: Re: Any objections to including the database schema unique id patch?
- From: "Chris Travers" <..hidden..>
- Date: Tue, 12 Sep 2006 23:08:21 -0700
David, you are correct. Actually, no changes so far will break
SQL-Ledger except that there could be bad data in the database
and both programs do a version check on the db and refuse to run
if the db is too new. So you would have to hack the Form.pm to
change the version number. So yes, it is possible. No, it
is probably not adviseable.
On 9/12/06, David Tangye <..hidden..> wrote:
On Wed, 2006-09-13 at 11:33 +1000, Gavin Carr wrote:
> Is there value in trying to defer non-critical schema changes for a
> certain period of time while ledger-smb gets up and running?
Methinks it is way up, and running fast, looking at the amount of code
changes over the past hours and days.
We got off to a running start, I'm afraid. Our view, however, is
to change the schema incrimentally as much as possible so we don't have
to rewrite the entire application.
Most of the new features in the upcoming 1.1 release will be work that was commissioned by other customers for SQL-Ledger.
> I guess
> I'm wondering whether diverging the schema too quickly from SL
> becomes a barrier to trying out/adopting L-SMB? If I as an SL user
> know that I can just drop the L-SMB code base on top of my existing
> schema, try it out for a few days/weeks - even try them both out
> side by side for a while -
Correct me if I am wrong, but it seems to me that LedgerSMB is beyond
that point already.
See above. Yes unless you want to hack the Form.pm
> then that makes the migration process
> significantly less risky for me, particularly if I'm non-technical
> and/or conservative/risk-averse (i.e. accountants ;-) ).
dum-de-dum 'Star trekkin' across the universe; ever goin' forward, we
cannot find reverse' :-)
Working on a fixme.sql that will flag and partition errors so the
installation willl proceed and can be sorted out later. Note
though that these are *serious* problems that would pre-date the
migration and would certainly need to be dealt with sooner than later.
Metatron Technology Consulting