I was thinking about something like:
session.reload( [tile0, tile1, tile2], 'neighbors' ) for example.
That feature would be great because you don't necessary know what
relation you will need later when you do the first query (eagerload is
not enough)
or in the case:
class Tile(object):
How do I create a unique constraint with the declarative plugin
(latest version 0.5) ?
both:
__table_args__ = ( UniqueConstraint('region.x', 'region.y'),
{'mysql_engine':'InnoDB'} )
__table_args__ = ( UniqueConstraint(x, y), {'mysql_engine':'InnoDB'} )
don't work.
Thanks!
I often find myself wanting to do something like this:
for address in user.addresses:
if address.street == 123 Elm Street:
# there's an address from this street, so do something
break
else:
# do nothing; no addresses from that street
That could also be accomplished with
On Sep 14, 2008, at 1:28 PM, GustaV wrote:
I was thinking about something like:
session.reload( [tile0, tile1, tile2], 'neighbors' ) for example.
That feature would be great because you don't necessary know what
relation you will need later when you do the first query (eagerload is
not
Ulf Lamping schrieb:
Garry schrieb:
Wichtig ist hierfür, dass die bereits erfassten
Daten in den üblichen Anwendungen - insbesondere Garmin, Navipowm,.. -
angezeigt werden, was mit highway=construction nicht funktioniert!
Wir mappen nicht für die Renderer - ich kauf mir demnächst
