In my case I'm beginning with only a command prompt and python call to Appwizard.py. I have an ip or DNS name along with a trusted connection to a dbname/tablename to hook into.
The wizard dialog could enable username/password textbox controls if I choose the 'SQL Server authentication' radio button and keep the username/password textbox controls disabled if I choose a 'Windows authentication' radio button. Or, could the AppWizard just allow a text box to use my own complete connection string? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul McNett Sent: Tuesday, November 03, 2009 12:50 PM To: Dabo developers' list Subject: Re: [dabo-dev] Sql Server trusted connection Ed Leafe wrote: > On Nov 3, 2009, at 12:13 PM, Paul McNett wrote: > >>>> If I'm running AppWizard do I have the ability to connectInfo >>>> string manually ? >>> AppWizard creates a py script so I'm sure it can be done. I just >>> don't know where in the code to do it. I don't use AppWizard to >>> create programs - so I hope Paul (the author of AppWizard) has an >>> better answer. >> AppWizard creates pretty bare-bones dabo applications. If you want to >> do your own db connection without using the .cnxml file, that's easy: > > > What about if the only way to connect to the server is through an SSL > connection? AppWizard won't be able to get the basic table info to > create the app. Right but we were talking about modifying the generated files to support creating the connection info manually, which is what I answered. That said, I wasn't sure what if anything this would solve, other than perhaps getting any extra kwargs sent along to the adapter, but I don't think it works that way. > John proposed a catch-all solution, but I think that's going to be > hell to implement and maintain. What we really need is a list of any > of the "extra" parameters that we need to support for each backend, > and the format that the server expects to get them. This way we can > update the CxnEditor to properly display that appropriate options for > each backend. I don't like the "extra" parameters thing at all. If postgressql takes 'sslmode' and mysql takes 'sslstyle' and MS SQL takes 'HKEY_SECURE_SOCKETS_LAYER_VERSION_IN_USE' (<g>) none of that should be exposed to our appdevs. It should just be 'ssl' or something simple and consistent for the purpose of the cnxml file, and for the parameters accepted to dabo.db.connect(). That said, I think it would be fine to accept **kwargs to dabo.db.connect() and pass them along to the adapter, but I don't think any extra parameters should be part of the cnxml file, unless it becomes necessary to do it that way, which I'm just not seeing. Paul [excessive quoting removed by server] _______________________________________________ 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/9a745764a58ad94d996a055d92d7012bd48df...@mspm1bmsgm20.ent.core.medtronic.com
