Re: Dbmail 3.2.0 error from automigrations

Fixed it. Silly mysql side-effects when re-using an open database
connection. Worked perfectly on postgres. Now both work by re-opening a
database connection while looping over the upgrade steps.

Please test HEAD on the dbmail_3_2 branch, if you can and let me now if
it solves things.


http://git.dbmail.eu/paul/dbmail/log/?h=dbmail_3_2


On 08-09-14 14:50, Thomas Raschbacher wrote:
> Am 29.08.2014 18:40, schrieb Paul J Stevens:
>> Looks like there is a problem here. Will investigate asap.
>>
>> On 28-08-14 08:09, Thomas Raschbacher wrote:
>>> Hi.
>>>
>>> I was just going to add 3.2.0 to the gentoo portage tree, but when
>>> testing i got this error in my syslog:
>>>
>>> dbmail/imap4d[15315]: Error:[db] check_upgrade_step(+920): SQLException:
>>> FEHLER:  Relation »dbmail_upgrade_steps« existiert nicht
>>> LINE 1: SELECT 1=1 FROM dbmail_upgrade_steps WHERE from_version = $1...
>>>
>>> Looks like the contents of
>>> /usr/share/doc/dbmail-3.2.0/sql/postgresql/upgrades/32001.psql.bz2 did
>>> not get applied to the db.
>>>
>>> I thought this was going to be applied automatically?
>>>
>>> Regards,
>>>   Thomas R
> 
> Any news on this yet? otherwise I will change the ebuild not to bz2 the
> sql files and commit it so that we have an up2date ebuild in teh portage
> tree.
> 
> Regards
> 
> 
> _______________________________________________
> DBmail mailing list
> [email protected]
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
> 

-- 
________________________________________________________________
Paul J Stevens       pjstevns @ gmail, twitter, github, linkedin
           www.nfg.nl/[email protected]/+31.85.877.99.97