Ed Leafe wrote: > On Feb 9, 2009, at 12:37 PM, Uwe Grauer wrote: > >> Further testing reveals that even if i use >> app.addConnectFile(myconnectfile) in the main application file, >> Dabo still might use other connection definition files found >> instead of myconnectfile which i added in the main application file. >> >> Given that Dabo searches a whole lot of extra paths prior to using the >> explicit connFile i think this has to be changed in a way where the >> explicitly added connection definition file will be used first, before >> other automatically found files are used. >> >> At least dApp.addConnectFile() needs a rewrite. >> I don't know if in addition other places would have to be changed. >> >> What do you think about this enhancement? > > > It sounds like all the enhancement requests to create ordered > dictionaries. Dicts are referenced by their keys; connections are > referenced by their names. They are stored internally as a dict with > the names as keys. This will not be changing, as the correct solution > is to give each different connection a different name.
If you even don't care about addConnectFile() not raising errors on wrong connFile settings, i will have to overwrite it in my ugApp(). Maybe i will have to specify my dConnection differently then with this weird connection specification design which searches the whole sys.path for a matching file name. Hopefully nobody will use Dabo for new python modules without overwriting the standard 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]
