[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos
From: |
Ian Haywood |
Subject: |
Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos |
Date: |
Fri, 24 Dec 2004 04:20:01 +1100 |
User-agent: |
Mozilla Thunderbird 0.8 (X11/20041012) |
Karsten Hilbert wrote:
Ah, there's the rub. That would mean you'd need to pull dummy
fields in the last query of _cmds_store_payload to match up
actual positions to positions in self._idx.
No, match the *names* of the new and old field name lists
One of us is confused here, maybe me, ....
OK, we start with:
self._payload = ['Ian', 'Haywood', ..., 123456]
self._idx = ['firstnames', 'lastnames', .... 'xmin_identity']
when we do _cmds_store_payload the final query returns
data= [123457]
idx = ['xmin_identity']
then why can't we do:
for i in range (0, len (idx)):
self._payload[self._idx.index (idx[i])] = data[i]
And how do you then know which position is which field ?
Certainly not by the original self._idx unless one pulls dummy
columns.
By the "idx" of this new query, its names match those in the original
self._idx
Ian
signature.asc
Description: OpenPGP digital signature
- [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Ian Haywood, 2004/12/21
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Karsten Hilbert, 2004/12/21
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Ian Haywood, 2004/12/21
- [Gnumed-devel] gmDemographics, Karsten Hilbert, 2004/12/22
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Karsten Hilbert, 2004/12/22
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Ian Haywood, 2004/12/22
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Karsten Hilbert, 2004/12/23
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos,
Ian Haywood <=
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Karsten Hilbert, 2004/12/23