dbenwit wrote:
The only issue is will this fix my problems mentioned in an earlier post.
I can't promise it will, but it's likely. The database schema and the code
must be kept in synch with one another.
Quote:
Am I to understand that I have been caught in the movement from the Beta version to RC1 version in the trunk?
Yes, that's pretty much it. It was an avoidable situation, but it would have been more work for the developers. Hopefully now more folks are using v1.4 an easy upgrade path will be maintained.
Quote:
I have A2Billing 1.4 Beta working properly on another box and I had done an update only a week or so ago and didn't need to do a database upgrade.
You did need to. Running a different schema than the code is designed for
will cause problems.
Quote:
Does this mean that before I checkout any more revisions from the trunk that I should upgrade the database from 1.4.0Beta to 1.4.0RC1?
Yes, but we're back to my previous answer: doing this is non-trivial and will require you to rewrite some SQL statements from CREATEs/INSERTs to ALTERs/UPDATEs.
Quote:
# mysqladmin -u root -p"root password" drop mya2billing
# install_db.sh (in the proper directory)
# mysql -u root -p"root password" < UPDATE-a2billing-v1.4.0-to-v1.4.1.sql
After DROPping the database you'll need to CREATE it again.