i am using the latest version (alembic 0.7.3). I still have the same error
even after adding the user_module_prefix configuration. it still uses sa.
as a prefix for types from sqlalchemy_utils.
On Monday, January 5, 2015 6:11:35 PM UTC+1, Michael Bayer wrote:
Ons mriba...@gmail.com
Well, the logic currently does this to determine if the type is a SQLAlchemy
type:
elif mod.startswith(sqlalchemy):
prefix = _sqlalchemy_autogenerate_prefix(autogen_context)
return %s%r % (prefix, type_)
else:
prefix = _user_autogenerate_prefix(autogen_context,
Lycovian mfwil...@gmail.com wrote:
I'm trying to take the first steps to implementing a test harness for my
custom dialect. The dialect in general works for basic functions
(DML/DDL/SELECT) but fails a majority of the unit tests in the standard
test suite as provided via the py.test
I'm trying to take the first steps to implementing a test harness for my
custom dialect. The dialect in general works for basic functions
(DML/DDL/SELECT) but fails a majority of the unit tests in the standard
test suite as provided via the py.test framework built into the dialect
boilerplate
Thank you Michael.
I've read the documentation that you quoted very carefully but still not
very sure in my case. You said that since 0.9.3 this issue has been
resolved, but I'm using 0.9.8 on Ubuntu and still get NullTypes. If I'm
using sqlalchemy MetaData.reflect() or automap extensions,
I ran in to a similar problem and was able to do something like this:
DBSession.execute(set @temp=0;)
DBSession.execute(Select @temp, ;)
I tried using the raw_connection but that ended up not working due to
different transactions. Above approach is working for now.
On Wednesday, December
Mike,
Thanks a lot for the response it really helped. I look forward to 1.0 and
having everything work automatically.
On Thursday, January 1, 2015 10:34:43 PM UTC-6, Michael Bayer wrote:
Michael Bayer mik...@zzzcomputing.com javascript: wrote:
best way is probably to add it on after the
