Sorry, forgot to mention, I had the same behaviour with SA 0.5.6 and
0.5.8.
Cheers,
Michael
On 15 Apr., 12:27, Michael Brickenstein brickenst...@mfo.de wrote:
Hi!
I have reflected my table from the db (Postgresql 8.4.2, tried psyco
2.0.12 and 2.0.14) using
Table(name, metadata,
On 15 Apr., 13:03, Michael Brickenstein brickenst...@mfo.de wrote:
Sorry, forgot to mention, I had the same behaviour with SA 0.5.6 and
0.5.8.
Cheers,
In former times, I used
prop.server_default to find out, that there is an default of ''.
Sorry, that's wrong it has always been the
On Apr 15, 2010, at 7:26 AM, Michael Brickenstein wrote:
On 15 Apr., 13:03, Michael Brickenstein brickenst...@mfo.de wrote:
Sorry, forgot to mention, I had the same behaviour with SA 0.5.6 and
0.5.8.
Cheers,
In former times, I used
prop.server_default to find out, that there is an
Hi!
Thanks for your very prompt
answer.
Unluckily, my mails were a little bit unprecise:
So, I wondered why the following happened:
prop = get_mapper(Participation).get_property('remark')
c=prop.columns[0]
c
Column(u'remark', PGText(length=None, convert_unicode=False,
assert_unicode=None),
On Apr 15, 2010, at 11:35 AM, Michael Brickenstein wrote:
Hi!
Thanks for your very prompt
answer.
Unluckily, my mails were a little bit unprecise:
So, I wondered why the following happened:
prop = get_mapper(Participation).get_property('remark')
c=prop.columns[0]
c
Hi!
Thanks, that was very helpful for me.
Cheers,
Michael
Am 15.04.2010 um 18:17 schrieb Michael Bayer:
this column is against an alias, which suggests you've mapped to an alias()
or select() of some kind. To get at full table metadata you need to be
talking to Column objects that are
