Hello,
And best wishes for 2010! I am the maintainer, Geert Vanderkelen, of
MySQL Connector/Python at Sun Microsystems.
First, thanks for taking MySQL Connector/Python and putting it in as a
dialect in SQL Alchemy, great stuff already! This will be great for
other projects using SQLAlchemy. Very
On Jan 4, 5:29 pm, Michael Bayer mike...@zzzcomputing.com wrote:
..
* Could you change the dialect name from 'myconnpy' to
'mysqlconnector' or something like that. 'MySQL' should be first in
the name, as this is most 'official' thing the MySQL Team has done for
Python. Would be great.
geertjanvdk wrote:
Thanks so much for this! I think that name will make it more clear
what it is. There was additional myconnpy import in __init__.py,
which I corrected in the patch below.
oops, yeah , that is in r6615 thx
One change I did was _get_server_version_info(), see in patch
Thanks for the quick changes there!
On Jan 4, 7:45 pm, Michael Bayer mike...@zzzcomputing.com wrote:
..
For MySQL dialects there should be no errors or failures - at most there
may be a handful of errors/failures which correspond to tests that should
be skipped for that DBAPI, although if
Hi Mike,
Thank you very much for replying to my post. I really appreciate it.
I agree that the init of the classes may have something to do with the
problem.
Maybe the way we are defining the attributes does not allow to
SQLAlchemy table
wrappers to view the attributes' values?
What confuses me
Here goes the variables' parent class
#===
# Variable quantities with units
# Written by Konrad Hinsen hin...@cnrs-orleans.fr
# with contributions from Greg Ward
# last revision: 2007-5-25
# Revised for SIAM-PFM by Paul
seth wrote:
Hi Mike,
Thank you very much for replying to my post. I really appreciate it.
I agree that the init of the classes may have something to do with the
problem.
Maybe the way we are defining the attributes does not allow to
SQLAlchemy table
wrappers to view the attributes'
