Michael,
You are right, I have been using "String" with no length when I want a
CLOB column and "Unicode" for varchar2 datatypes in my Entity
definitions (using Elixir).
I'll change my model to explicitly use UnicodeText.
N.B.
This change in behaviour is noted in the 05Migration notes as you say,
but the v5 documentation for the String type does not yet reflect
this.
Thanks very much,
Tim
On Sep 26, 4:51 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Sep 26, 2008, at 11:23 AM, picoplex wrote:
>
>
>
>
>
> > The code that chokes with SA 0.5.0rc1 is as follows:
>
> > filteredRecords =
> > theChildClass
> > .query().filter(filterString).join(relationshipToParentName,
> > aliased
> > =requiresAliased).filter(parentFilterString).order_by(orderByString)
> > [start:(start+limit)]
>
> > where:
> > theChildClass: blnver
> > filterString: '1=1'
> > relationshipToParentName: 'childblnvers'
> > requiresAliased: True
> > parentFilterString: 'blnver.id=1'
> > orderByString: u'blnver.name ASC'
>
> > (In debugging I noted that the orderByString is a unicode string
> > (unintentional), whereas all the others are plain strings)
>
> > I have just checked that SA version 0.4.5 does not have this problem
> > on Linux either.
>
> > Please let me know if you need more information.
>
> What I need to know specifically is the kinds of types which are
> assembled on your Table objects. Basically, the difference here is
> between:
>
> t = Table('mytable', metadata, ..., Column('foo', Text))
>
> versus
>
> t = Table('mytable', metadata, ..., Column('foo', String(50))
>
> My suspicion is that you are declaring a column like this:
> Column('foo', String). In 0.4, this would produce a Text type, which
> in Oracle will do the proper LOB handling. In 0.5, the implicit
> switch from "String" with no length to "Text" is gone (mentioned in
> the migration doc), so in this case you'd have a String column which
> does not expect a LOB object.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
