I don't know if its a bug or i am missing out on something, since i didn't
ran into similar issue before.
Here is the scenario, my form creates 3 tables in ODK_PROD, i.e.
Client Core
House Hold Members
House Hold Members Signatures (blb)
I am able to uniquely identify/query 'House Hold Members' for a client
using _TOP_LEVEL_AURI column in it. But 'House Hold Members Signatures'
column TOP_LEVEL_AURI contains same values as 'Client Core' _URI column
(instead it should have been 'House Hold Members' _URI column values to
uniquely identify member signatures and as it is logically Top Level URI to
it as well). This makes it impossible to identify member images associated
with them.
Any ideas on how to deal with such problem? Usually TOP_LEVEL_AURI / PARENT
column has all what it needs, but its weird how ODK generated database
columns this time.
The _ref table links the _blb to the _bin table, and the _bin table then
links into the 'House Hold Members' table.
ยทยทยท
On Mon, Feb 24, 2014 at 9:54 AM, Ayub wrote:
HI ODK Devs,
I don't know if its a bug or i am missing out on something, since i didn't
ran into similar issue before.
Here is the scenario, my form creates 3 tables in ODK_PROD, i.e.
Client Core
House Hold Members
House Hold Members Signatures (blb)
I am able to uniquely identify/query 'House Hold Members' for a client
using _TOP_LEVEL_AURI column in it. But 'House Hold Members Signatures'
column TOP_LEVEL_AURI contains same values as 'Client Core' _URI column
(instead it should have been 'House Hold Members' _URI column values to
uniquely identify member signatures and as it is logically Top Level URI to
it as well). This makes it impossible to identify member images associated
with them.
Any ideas on how to deal with such problem? Usually TOP_LEVEL_AURI /
PARENT column has all what it needs, but its weird how ODK generated
database columns this time.