This question is locked. New answers and comments are not allowed.
Hello,
the automatic mapping of OpenAccess is quite comfortable in most situations, but in a migration scenario it is important to know what member is mapped to what column.
Say in Version 1 3 members (m1, m2, m3) are references that are mapped to columns named id2, id3, id4. How can we be sure that those members are mapped to the same columns in a Version 2 ? Vschema will check the schema changes. But what happens if a database created with Version 1 is accessed by a Version 2 application ? The columns would be the same, but the mapping may not!
How can we get knowledge of the member-mapping and how can this process be controlled by us ?
Thanks, Martin
the automatic mapping of OpenAccess is quite comfortable in most situations, but in a migration scenario it is important to know what member is mapped to what column.
Say in Version 1 3 members (m1, m2, m3) are references that are mapped to columns named id2, id3, id4. How can we be sure that those members are mapped to the same columns in a Version 2 ? Vschema will check the schema changes. But what happens if a database created with Version 1 is accessed by a Version 2 application ? The columns would be the same, but the mapping may not!
How can we get knowledge of the member-mapping and how can this process be controlled by us ?
Thanks, Martin