Hello, I've been trying to use the usrloc attributes feature to store and retrieve additional data per location. This works for in-memory tables, but not when db_mode=DB_ONLY. The attached patch adds this so the xavps are restored when doing a DB lookup for a single aor.
Is this a bugfix for an incomplete feature or do I need to wait for the thaw before committing?
Regards, Hugh ________________________________ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
Waite, Hugh writes:
I've been trying to use the usrloc attributes feature to store and retrieve additional data per location. This works for in-memory tables, but not when db_mode=DB_ONLY. The attached patch adds this so the xavps are restored when doing a DB lookup for a single aor.
Is this a bugfix for an incomplete feature or do I need to wait for the thaw before committing?
i would vote for a bug fix if the feature works for in-memory tables and readme does not tell that it does not work in db-only mode.
-- juha
On 24/09/14 15:29, Juha Heinanen wrote:
Waite, Hugh writes:
I've been trying to use the usrloc attributes feature to store and retrieve additional data per location. This works for in-memory tables, but not when db_mode=DB_ONLY. The attached patch adds this so the xavps are restored when doing a DB lookup for a single aor.
Is this a bugfix for an incomplete feature or do I need to wait for the thaw before committing?
i would vote for a bug fix if the feature works for in-memory tables and readme does not tell that it does not work in db-only mode.
it can be committed - it fixes to a proper behaviour for attrs in db only mode. Cheers, Daniel