Revision 0b33cc60
Von Moritz Bunkus vor etwa 9 Jahren hinzugefügt
SL/DB/MetaSetup/FollowUp.pm | ||
---|---|---|
__PACKAGE__->meta->allow_inline_column_values(1);
|
||
|
||
__PACKAGE__->meta->foreign_keys(
|
||
created_by => {
|
||
created_by_employee => {
|
||
class => 'SL::DB::Employee',
|
||
key_columns => { created_by => 'id' },
|
||
},
|
||
|
||
created_for => {
|
||
created_for_employee => {
|
||
class => 'SL::DB::Employee',
|
||
key_columns => { created_for_user => 'id' },
|
||
},
|
scripts/rose_auto_create_model.pl | ||
---|---|---|
orderitems => { parts_id => 'part', trans_id => 'order', },
|
||
delivery_order_items => { parts_id => 'part' },
|
||
invoice => { parts_id => 'part' },
|
||
follow_ups => { created_for_user => 'created_for', created_by => 'created_by', },
|
||
follow_ups => { created_for_user => 'created_for_employee', created_by => 'created_by_employee', },
|
||
follow_up_access => { who => 'with_access', what => 'to_follow_ups_by', },
|
||
|
||
periodic_invoices_configs => { oe_id => 'order' },
|
Auch abrufbar als: Unified diff
S:D:FollowUp: Namen der Relationen created_by…/created_for… eindeutig gemacht
Die Spalten heißen leider created_by und created_for_user. Damit es bei
der Benutzung nicht zu Verwirrungen zwischen Spaltennamen und den Namen
der Relationships kommt, werden die Relationshipnamen schlicht eindeutig
umbenannt.
Bisher hat kein Rose-Code diese Relationships genutzt. Nur der
CustomerVendor-Controller hat die Spaltennamen benutzt.