I have started to get this error on some machines I deploy my
application to, but not on my own machine. As far as I can see it is
running the same verison of SQLAlchemy (0.5.8) and MySQLdb (1.2.2), so
I have a hard time understanding the issue. Any Ideas on what could be
causing it?
Traceback
Hello all,
always with the following:
orm.mapper(Human, table.human)
orm.mapper(Content, table.content,
polymorphic_on = table.content.c.content_type_id,
properties = {
'owner' : orm.relationship(
Human,
lazy = 'joined',
innerjoin = True,
Hello. I'v got an problem
I have a string like 'john' and I need to get results for 'john, JOHN'
etc. How to do that?
--
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
forget it, I missed this in the docs :
Note that when using joined eager loaders with relationships, the
tables used by the eager load’s join are anonymously aliased. You can
only order by these columns if you specify it at the relationship()
level. To control ordering at the query level
I figured this one out, I had tried to create a attribute synonym by
doing this:
class alaID(Base):
Grouped products
__tablename__ = al_ids
__table_args__ = {'schema':'review', 'useexisting':True}
[...]
generated_name = column_property(select([master_name], al_id ==
On 6/23/2010 5:28 AM, Alexander Zhabotinskiy wrote:
Hello. I'v got an problem
I have a string like 'john' and I need to get results for 'john, JOHN'
etc. How to do that?
I think perhaps the ilike() filter operator might be the only way? It
might even depend on your back-end.
Hi Alexander,
On 23/06/2010 12:28, Alexander Zhabotinskiy wrote:
Hello. I'v got an problem
I have a string like 'john' and I need to get results for 'john, JOHN'
etc. How to do that?
I do it like this. force db column and search string to upper and I put
a % before and after the search
Hi,
we are about upgrading our sqlalchemy library from 0.4.8 to something
newer and during this process we have detected that the LIMIT/OFFSET
support for oracle has been changed, from using “ROW NUMBER OVER...”
to a wrapped subquery approach in conjunction with ROWNUM as described
in
On Wed, Jun 23, 2010 at 1:50 AM, Ralph Heinkel ralph.hein...@web.de wrote:
Hi,
we are about upgrading our sqlalchemy library from 0.4.8 to something newer
and during this process we have detected that the LIMIT/OFFSET support for
oracle has been changed, from using “ROW NUMBER OVER...” to a
On Jun 23, 2010, at 3:50 AM, Ralph Heinkel wrote:
Hi,
we are about upgrading our sqlalchemy library from 0.4.8 to something newer
and during this process we have detected that the LIMIT/OFFSET support for
oracle has been changed, from using “ROW NUMBER OVER...” to a wrapped
subquery
Hi Torsten,
How would you define the Account class? Calling create on my
DeclarativeBase Account object was one of the first things I tried,
but I keep getting:
AttributeError: type object 'Account' has no attribute 'create'
Maybe a version difference in sqlalchemy?
- Shane
On Jun 18, 10:22
11 matches
Mail list logo