1.9.6, 2.0 releng, schedule proposal

cxl000 at hotmail.com cxl000 at hotmail.com
Tue May 9 02:29:40 EDT 2006


Chris Shoemaker wrote:
> On Mon, May 08, 2006 at 10:10:23AM +0200, Christian Stimming wrote:
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Josh Sled schrieb:
>>>   - PostGres support
>>>     - configure.in/building support
>>>     - Open/Save (more of a "don't do anything else"; Bug#332251).
>>>       
>> *sigh* I'm not at all a postgresql user/developer, but if we remove/hide
>> this, it would be a feature regression compared to 1.8.x. I'd strongly
>> vote to keep it enabled, but #332251 certainly is a showstopper for that...
>>     
>
> I could probably fix #332251, but look at #313696.  The only reason to
> do anything with pg right now, IMO, would be to allow the immediate
> export to xml, but that's been impossible at least as far back as
> 1.8.11.  So, IMO, there's no point in fixing #332251 unless we're
> committed to fixing #313696 as well, and I have no idea how difficult
> that would be.  :(
>   
There needs to be a method for people who use pg to migrate there to
gnucash 2. If fixing #332251 will allow gnucash 2 to use an existing 1.8
pg database, albeit with the same restrictions no SX, business, budgets
etc then this is sufficient.
The lack of a save as xml option means that the user needs to be
responsible for performing a backup using pg tools when upgrading to
gnucash 2.
If the schema in pg has not changed during 1.8 then an earlier 1.8
version may be able to save data to an xml file. The pg load/xml save
from this earlier version could be used to produced a once of migration
tool allowing people to convert to the fully supported backend to gain
access to the new features.

Regards,
      Chris


More information about the gnucash-devel mailing list