[Dbconfig-common-devel] Re: Bug#397089: dbconfig-common: migration fails when dbconfig-load-include returns empty values

[Matt Brown]

sean finney wrote:

> what if the app is a single dbtype application (and thus always has
> dbc_dbtype set)?  otherwise, i agree with the approach, and it cleans
> up the state machine area quite a bit which is a good thing.

Hmm, that could be a problem yes. Unfortunately I'm not familiar with
all the nuances of dbconfig-common to know what a good solution to this
is. I could check every return value from dbconfig-load-include and only
error out if they are all blank, or we could get more sophisticated and
check only the required values for the selected database type...

Perhaps the real solution is to make dbconfig-load-include only act as
hints and have the user still asked the questions...

I have time to work on a patch, but I'll need your expertise and
knowledge of the code to suggest which approach fits in best.

Cheers

-- 
Matt Brown
Debian Developer
mattb at debian.org
Mob +64 21 611 544 www.mattb.net.nz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20061107/0669c3a8/signature.pgp