Daniel Robbins wrote: > On Thu, Mar 4, 2010 at 11:34 AM, Chris Withers <ch...@simplistix.co.uk> > wrote: >> Hi All, >> >> I'm looking to create a model with a unicode or string column type that >> is >> case sensitive. >> >> I'm looking to do this in the model in such a way that the code in the >> model >> doesn't know or care about what backend database is used, but that barfs >> if >> it's ever used with a backend that doesn't actually support >> case-sensitive >> strings or unicodes. >> >> The current set of back ends we're targeting is (MySQL,sqlite)... >> >> How do I do this? > > I think all databases that SQLAlchemy supports (in fact, likely all > databases in use today) support case-sensitive strings by default, so > I don't know if this something you'll need to worry about in your > code. Maybe I am misunderstanding what you are trying to do?
hes likely referring to case-sensitive collation support. Build a TypeDecorator and intercept the "dialect" in the process_bind_param() method. > > -Daniel > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
