Sorry, I haven't touched that issue recently. Where I should turn on
'echo=true', in module or migration script? I saw 'create_engine' has this,
but I didn't directly use 'create_engine'.
SHOW CREATE TABLE gave something back to me:
utf8_general_ci is default collation rule in charset utf8.
Please ignore it, actually you are right, when I changed to collation
'utf8_unicode_ci', it works perfectly fine.
Thanks a lot!
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To view this discussion on the web visit
On Thu, 2012-12-06 at 17:43:45 -0800, junepeach wrote:
How to upgrade to a newer sqlalchemy version? I can not find a related
document. Should I just use pip to install the current one? Will both
version conflict?
The answer depends on how and where SA is installed already. The best
way IMHO
Thank you Mike and Audrius, this is very helpful. I have installed
SQLAlchemy 0.8.0b1 and tried the code Mike gave to me:
Base = declarative_base()
def character_type(length):
return String(length).with_variant(String(length,
collation='utf8_general_ci'),
On Dec 7, 2012, at 4:01 PM, junepeach wrote:
Thank you Mike and Audrius, this is very helpful. I have installed
SQLAlchemy 0.8.0b1 and tried the code Mike gave to me:
Base = declarative_base()
def character_type(length):
return String(length).with_variant(String(length,
Mike,
Thanks very much for your quick response. Now it works, sqlite works
fine, and the result from mysql seems not exact what I need, see below.
..
from sqlalchemy.types import TypeDecorator, String
class character_type(TypeDecorator):
def __init__(self, length):
self.impl
On Dec 7, 2012, at 5:01 PM, junepeach wrote:
Mike,
Thanks very much for your quick response. Now it works, sqlite works fine,
and the result from mysql seems not exact what I need, see below.
..
from sqlalchemy.types import TypeDecorator, String
class
Thanks, this is nice, I will use it in my code.
On Thursday, December 6, 2012 3:17:25 PM UTC-5, junepeach wrote:
For case insensitive columns:
MySQL - use utf8_general_ci
SQLite - use NOCASE collation
Can migration tool handle that for most databases or it should be better
done in
I tested my code, and got below:
Traceback (most recent call last):
File /usr/local/bin/alembic, line 9, in module
load_entry_point('alembic==0.4.0', 'console_scripts', 'alembic')()
File /usr/local/lib/python2.7/dist-packages/alembic/config.py, line
255, in main
versionadded is 0.8
On Dec 6, 2012, at 4:36 PM, junepeach wrote:
I tested my code, and got below:
Traceback (most recent call last):
File /usr/local/bin/alembic, line 9, in module
load_entry_point('alembic==0.4.0', 'console_scripts', 'alembic')()
File
Oh, I see, mine is not sqlalchemy 0.8. Thanks.
--
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/-/dvjzhmyWicoJ.
To post to this group, send email to
How to upgrade to a newer sqlalchemy version? I can not find a related
document. Should I just use pip to install the current one? Will both version
conflict?
Thank you very much for your quick response and help!
JP
--
You received this message because you are subscribed to the Google Groups
12 matches
Mail list logo
