Thanks. Yes it works fine now.
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To view this discussion on the web visit
https://groups.google.com/d/msg/sqlalchemy/-/-Cx--STwfO4J.
To post to this group, send email to sqlalchemy@googlegroups.com.
To
hello list -
due to the very sad state of Python install tools, even though 0.8.0b1 is
hidden on pypi, and 0.7.9 remains the production release, apparently many
production system tools are going out and getting 0.8.0b1. This is incredibly
annoying, but 0.8.0b1 is now on Sourceforge only
I have a few questions about using the mysql dialect index options
(http://docs.sqlalchemy.org/en/latest/dialects/mysql.html#mysql-indexes)
First, do you need to import anything special in order to use the options?
(Is there a subclass of Index in the mysql dialect? or will using the base
Congrats Mike for all this great work!
2012/10/30 Michael Bayer mike...@zzzcomputing.com
The first beta release of the SQLAlchemy 0.8 series, 0.8.0b1, is released
for developer evaluation.
0.8 represents the latest series of refinements to the SQLAlchemy Core and
ORM libraries and features
Hi Michael,
I have several views defined in alembic migration script, and so I defined
op.execute('drop view xxx') to drop all of my view sql files. When I ran script
'alembic downgrade -1' to drop all of the tables, views, indexes, MySQL,
SQLITE3 worked fine. When working with Postgresql, I
On Oct 31, 2012, at 4:32 PM, junepeach wrote:
Hi Michael,
I have several views defined in alembic migration script, and so I defined
op.execute('drop view xxx') to drop all of my view sql files. When I ran
script 'alembic downgrade -1' to drop all of the tables, views, indexes,
MySQL,
A big thank you to Mike and all the other contributors, for what is a
shining example of usefulness, quality and excellence!
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To view this discussion on the web visit
I find the answer that I need to use the utf_bin during the Column
definition.
Something like below:
code = Column(VARCHAR(10, collation='utf8_bin'), nullable = False)
then I can get the case sensitive support from the query filter.
DoDo於 2012年10月27日星期六UTC+8下午11時41分06秒寫道：
I try to use
