FollowUp(Access)-Rose-Models: sinnvollere Namen für Relationships

[mfinanz.git] / SL / DB / MetaSetup / FollowUpAccess.pm

diff --git a/SL/DB/MetaSetup/FollowUpAccess.pm b/SL/DB/MetaSetup/FollowUpAccess.pm
index 55c6f5f145f994c3454d7fb5b0f8ca61e8a3f625..c2fccb1e96ac98739dcc48af73953995c22fe554 100644 (file)
--- a/SL/DB/MetaSetup/FollowUpAccess.pm
+++ b/SL/DB/MetaSetup/FollowUpAccess.pm
@@ -9,26 +9,24 @@ use base qw(SL::DB::Object);
 __PACKAGE__->meta->table('follow_up_access');
 
 __PACKAGE__->meta->columns(
-  who  => { type => 'integer', not_null => 1 },
-  what => { type => 'integer', not_null => 1 },
   id   => { type => 'serial', not_null => 1 },
+  what => { type => 'integer', not_null => 1 },
+  who  => { type => 'integer', not_null => 1 },
 );
 
 __PACKAGE__->meta->primary_key_columns([ 'id' ]);
 
 __PACKAGE__->meta->foreign_keys(
-  employee => {
+  to_follow_ups_by => {
     class       => 'SL::DB::Employee',
-    key_columns => { who => 'id' },
+    key_columns => { what => 'id' },
   },
 
-  employee_obj => {
+  with_access => {
     class       => 'SL::DB::Employee',
-    key_columns => { what => 'id' },
+    key_columns => { who => 'id' },
   },
 );
 
-# __PACKAGE__->meta->initialize;
-
 1;
 ;