Feature for discussion (with patch): pymssql_shell about pymssql

[GoogleCodeExporter]

I'd say its best to not have this directly in the library.  However, I see no 
problem with creating a new package called pymssql-shell for it.  Have it 
depend on pymssql and you end up with basically the same situation, but without 
a commitment from pymssql to maintain it.  My two reasons for thinking this way 
are:

- hard enough to get time to maintain the library, lets not commit the project 
to doing any more than is absolutely necessary for a working mssql driver.  
Even though its simple now, if people start using it, it will inevitable not 
work as it should, require bug fixes, etc.
- now you have a library package with an application embedded in it.  Seems 
best to leave the library a library and let the application stand on its own, 
using the library.

Also, I'm wondering if there are any projects already out there that do 
something like this for any DBAPI compliant driver.

I'm going to set to WontFix, since you weren't sure in the first place.  But if 
you think I'm missing something, feel free to object.  :)

Original comment by [email protected] on 7 Feb 2013 at 2:07

• Changed state: WontFix

[GoogleCodeExporter]

Thanks Randy.

That makes total sense. That's an interesting idea to make it work with any 
DBAPI driver. I lifted the code for this out of another program I wrote that 
uses SQLAlchemy as the abstraction layer:

https://github.com/msabramo/sqlalchemy_sql_shell

But it probably could be generalized to talk to either SQLAlchemy or DBAPI.

Original comment by [email protected] on 13 Feb 2013 at 3:40