Ed Leafe wrote:
> On Feb 7, 2009, at 4:51 AM, Uwe Grauer wrote:
>
>> In one of my apps i use a cnxml file called "fwadm.cnxml".
>> I specify the connection file when calling forms:
>> frm = BrwPerForm(CxnName="fbtool_dev", CxnFile="path://fwadm.cnxml")
>>
>> When i tested something, i temporary created a file "xx.cnxml" which
>> contained the same connection name ("fbtool_dev") but for a sqlite db.
>>
>> My app stopped working because now Dabo somehow took the connection
>> settings from xx.cnxml instead of the settings from the specified file
>> fwadm.cnxml.
>> After removing xx.cnxml my app is working again.
>>
>> Before i start debugging this to find out what's going wrong,
>> do you have any ideas on why Dabo does this sort of magic?
>
>
> Dabo maintains a dict of connections keyed on name. It loads
> all .cnxml files in the current folder, as well as the standard db
> directory at startup.
>
> The CxnFile property tells Dabo to load that file if it isn't already
> loaded. I'm assuming that since it had already loaded at startup, this
> was ignored when the form opened, and the connection named
> 'fbtool_dev' was used.
>
Ok, but i don't think that this makes any sense.
I explicitly told Dabo to use fwadm.cnxml.
I could understand a automatic searching for a connection name if
there wasn't specified the connection file explicitly but i think it is
a bug if Dabo overwrites a connection specification just because there
is a second file which includes the same connection name.
Implicit automatic management is ok as long as it doesn't produce faulty
behavior.
Uwe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[email protected]
