[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos |
Date: |
Wed, 22 Dec 2004 09:12:11 +0100 |
User-agent: |
Mutt/1.3.22.1i |
> >>Karsten, do we really need this?
> >>Why not just insist the last query of _cmds_store_payload return the
> >>XMINs with their correct names using the "select...foo as bar..." syntax?
> >
> >That is what we do. However, we also need to know where to put
> >them in self._payload. How else would we handle that ?
> self._idx.index ()
Uhm, OK, _refetch_payload pulls, say, 6 fields, the last of
which (eg idx=5) being xmin_something. The index to that query
becomes self._idx.
_store_payload in the very last query pulls xmin_something
again - but now it would have the index 0 in the result. How
are we to reconcile that ? Do you suggest to adjust for the
index by pulling dummy columns, eg in the example do
select null, null, null, null, null, xmin_something where ...
as the very last query in _cmds_store_payload such that
self._idx will fit ?
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [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 <=
- 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, 2004/12/23
- Re: [Gnumed-devel] gmBusinessDBObject._xmins_refetch_col_pos, Karsten Hilbert, 2004/12/23