On Nov 3, 2009, at 2:32 PM, John wrote:
>> Or, could the AppWizard just allow a text box to use my own complete
>> connection string?
>
> Oh a catch 22 you can't use AppWizard because it needs to connect to
> the DB
> and you can't connect to DB because it requires Trusted = True.
>
> How about installing MsSQL Express on your machine, create a copy of
> the real
> DB, create the AppWizard script. Then edit the script to change the
> connectinfo to allow you to connect to the real DB.
No, the answer is to get a better understanding of just what each
backend would need, and adjust the interface dynamically. That's why a
general "pass the kwargs" solution is not a good idea: we need to know
what the options are.
> The only issue I discovered with the patch is that Ed also
> passed 'ForceCreate' via the same means. It caused me to pop() Ed's
> parameter off the stack. Actually, I don't understand why Ed passed
> the
> parameter to the all the DB adapters when it only applies to SQLite.
Actually, the fact that the blindly-passed parameter required you to
do all sorts of cleanup code should have been a tip-off that it isn't
a good solution. The reason that forceCreate was done that way was
that it was a hastily-thrown-together approach to solve a particular
problem. Now that we have seen that we need to pass even more
information, it's obvious that a refactoring is needed, and that
forceCreate and any other params need to be explicit.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
