On Jun 14, 2007, at 9:16 AM, Andreas Jung wrote:

>
> This happens when _convert_key() is called with
> key='arbeitsmittelhierarchy_arbeitsmittel_view.stammdatenverwaltung_ta 
> uglich'
>

im confused.  are you passing that string directly to row[<some  
key>] ?  result column names cant have periods in them.

> When I look at the self._ResultProxy__keys then the key cache contains
> shortend col names:
>
>
> (Pdb) for x in  self._ResultProxy__keys:print x
> arbeitsmittelhierarchy_arbeitsmittel_view_idautor
> arbeitsmittelhierarchy_arbeitsmittel_view_idsachgebiet
> arbeitsmittelhierarchy_arbeitsmittel_view_num_hre
> arbeitsmittelhierarchy_arbeitsmittel_view_bemerkung
> arbeitsmittelhierarchy_arbeitsmittel_view_versionsnr
> arbeitsmittelhierarchy_arbeitsmittel_view_idzielgruppe
> arbeitsmittelhierarchy_arbeitsmittel_view_idfassung
> arbeitsmittelhierarchy_arbeitsmittel_view_dateiname
> arbeitsmittelhierarchy_arbeitsmittel_view_originalname
> arbeitsmittelhierarchy_arbeitsmittel_view_rechnerstand
> arbeitsmittelhierarchy_arbeitsmittel_view_id
> arbeitsmittelhierarchy_arbeitsmittel_view_hidx_master
> arbeitsmittelhierarchy_arbeitsmittel_view_stammdatenverwaltung_
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
> Using SA 0.3.8 and Postgres 7.4.7...what's the suggested way
> to get around this issue (shortening the column names isn't an
> option).

using column labels or using Column objects to get at the value.

result = select([table.c.longcolumnname.label('foo')]).execute()
result.fetchone()['foo']

or

result = select([table.c.longcolumnname]).execute()
result.fetchone()[table.c.longcolumnname])


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to