Re: Calling all testers: 1.1 now in feature freeze

["Chris Travers" <..hidden..>]

One more thing regarding older PostgreSQL support:
There doesn't seem to be very many major reasons not to upgrade to
8.x.  If people find that there are reasons not to do so (large
databases with long restore times), then it isn't hard to add 7.4
support by replacing lines like:

ALTER TABLE acc_trans ALTER COLUMN amount TYPE NUMERIC;

with something like:
ALTER TABLE acc_trans ADD COLUMN amount_new NUMERIC;
UPDATE TABLE acc_trans SET amount_new = amount;
ALTER TABLE acc_trans DROP COLUMN amount;
ALTER TABLE acc_trans ALTER COLUMN amount2 RENAME TO amount;

Obviously this gets far more complex as you get back before PostgreSQL 7.3.

People can correct me if I am wrong but when 8.2 is released, I
believe that 7.3 will no longer be actively maintained by the core
community, which means roughly a year  more of 7.4 support from the
core PostgreSQL development team.

If there is enough call for it, I suppose we could support 7.4 for
while longer, but I would rather see such support come from the
community at large so that our core team can focus on versions that
will be supported by the PostgreSQL community for a while longer.  In
this case, this means 8.0 and higher.

Best Wishes,
Chris Travers

On 9/18/06, Chris Travers <..hidden..> wrote:
> Hi Seneca;
>
> Added to the bug tracker.  Will get this one resolved tonight.  Will
> probably just apply your patch outright.  This will mean that dataset
> creation may be broken in other ways as well.
>
> Thanks,
> Chris Travers
>
> On 9/18/06, Seneca Cunningham <..hidden..> wrote:
> > On 18-Sep-2006, at 16:51 :35, Chris Travers wrote:
> > >
> > > Anyone who would like to test the software should feel free to do so.
> > > Note that we recommend doing so on a testing server as some things
> > > like dataset creation require connections to template1 (which we
> > > really don't want to get messed up).
> > >
> >
> > I tried reaching you on IRC earlier, but the schema upgrade script
> > broke on my test box (LedgerSMB 1.0 upgraded from SQL-Ledger 2.6.17,
> > no other patching).  It also does not work with PostgreSQL versions
> > 7.4.x and earlier (pre-8.x does not support altering column types).
> >
> > I have attached a patch for the problems I encountered with my 8.1
> > backend.
> >
> >    1) chart lacked a primary key, so id is now set as one as is required
> >       by the foreign key
> >    2) typoed table name adding ar ids to transaction_ledger
> >    3) adjusted the add_custom_field function to successfully add more
> > than
> >       one custom field to a given table without erroring out
> >    4) fix a variable name in drop_custom_field so that it works
> >
> > I haven't written a patch for Pg-functions.sql with my fixes yet.
> >
> >
> >
> >
> > --
> > Seneca Cunningham
> > ..hidden..
> >
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys -- and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> >
> > _______________________________________________
> > Ledger-smb-devel mailing list
> > ..hidden..
> > https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
> >
> >
> >
> >