Switch to: V10V9V8V7V6V5

Differences

This shows you the differences between two versions of the page.

valentina:tips:vstudio:fill_fk [2017/05/06 20:28]
rz
valentina:tips:vstudio:fill_fk [2017/05/09 15:53] (current)
rz
Line 8: Line 8:
**Problems** with this approach are: **Problems** with this approach are:
-  * This is additional query of kind "SELECT PKfld FROM A".  +  * This is the additional query of kind "SELECT PKfld FROM A".  
-  * This can be very big list actually, equal to the number of records in the table A (so even million records). +  * This can be very big list actually, equal to the number of records in table A (so even million records).
  * If PK is a synthetic key (e.g. 1,2,3,...) this not helps at all, and they show 1 or 2 other fields, which should help you identify correct record.   * If PK is a synthetic key (e.g. 1,2,3,...) this not helps at all, and they show 1 or 2 other fields, which should help you identify correct record.
Line 16: Line 16:
  * In the top Data Editor you keep table A, in the bottom Data Editor you keep table B.   * In the top Data Editor you keep table A, in the bottom Data Editor you keep table B.
  * You can locate a parent record in the table A quite easy using e.g. Filter of Data Editor. And you see all fields of Table A so easy can identify correct one.   * You can locate a parent record in the table A quite easy using e.g. Filter of Data Editor. And you see all fields of Table A so easy can identify correct one.
-  * In the bottom data editor click "New Record" button, and this immediately create a new record in the bottom Data Editor with FK field, automatically filled by PK value(s).+  * In the bottom data editor click "New Record" button, and this immediately creates a new record in the bottom Data Editor with FK field, automatically filled by PK value(s).
{{:valentina:products:vstudio:picts:data_editor_pk_fk_auto_fill.png|}} {{:valentina:products:vstudio:picts:data_editor_pk_fk_auto_fill.png|}}