X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2F05_Authentication.pod;h=8a7ec0648d705aeff66398204604259545f9e8b9;hp=5f378cc4e732e6e188e4098e35eec57c9c328dad;hb=4768184b3b277399116fbd53cae3697a9767fee5;hpb=da59dbea96454dbc53dc7bb5a813849bb35c6ab8 diff --git a/lib/Catalyst/Manual/Tutorial/05_Authentication.pod b/lib/Catalyst/Manual/Tutorial/05_Authentication.pod index 5f378cc..8a7ec06 100644 --- a/lib/Catalyst/Manual/Tutorial/05_Authentication.pod +++ b/lib/Catalyst/Manual/Tutorial/05_Authentication.pod @@ -81,10 +81,10 @@ add the role information here although it will not be used until the authorization section, Chapter 6). Create a new SQL script file by opening C in your editor and insert: - PRAGMA foreign_keys = ON; -- -- Add user and role tables, along with a many-to-many join table -- + PRAGMA foreign_keys = ON; CREATE TABLE user ( id INTEGER PRIMARY KEY, username TEXT, @@ -139,21 +139,27 @@ option on the DBIC model helper to do most of the work for us: $ ls lib/MyApp/Schema/Result Author.pm BookAuthor.pm Book.pm Role.pm User.pm UserRole.pm -Notice how the helper has added three new table-specific result source +Notice how the helper has added three new table-specific Result Source files to the C directory. And, more importantly, even if there were changes to the existing result source files, those changes would have only been written above the C<# DO NOT MODIFY THIS OR ANYTHING ABOVE!> comment and your hand-edited enhancements would have been preserved. -Speaking of "hand-editted enhancements," we should now add -relationship information to the three new result source files. Edit -each of these files and add the following information between the C<# -DO NOT MODIFY THIS OR ANYTHING ABOVE!> comment and the closing C<1;>: +Speaking of "hand-editted enhancements," we should now add the +C relationship information to the User Result Source file. +As with the Book, BookAuthor, and Author files in +L, +L has +automatically created the C and C relationships +for the new User, UserRole, and Role tables. However, as a convenience +for mapping Users to their assigned roles (see +L), we will +also manually add a C relationship. Edit +C add the following information between +the C<# DO NOT MODIFY THIS OR ANYTHING ABOVE!> comment and the closing +C<1;>: -C: - - # many_to_many(): # args: # 1) Name of relationship, DBIC will create accessor with this name @@ -162,9 +168,12 @@ C: # You must already have the has_many() defined to use a many_to_many(). __PACKAGE__->many_to_many(roles => 'user_roles', 'role'); - -The code for this update is obviously very similar to the edits we made to the -C and C classes created in Chapter 3. +The code for this update is obviously very similar to the edits we made +to the C and C classes created in Chapter 3 with one +exception: we only defined the C relationship in one +direction. Whereas we felt that we would want to map Authors to Books +B Books to Authors, here we are only adding the convenience +C in the Users to Roles direction. Note that we do not need to make any change to the C schema file. It simply tells DBIC to load all @@ -173,16 +182,15 @@ C directory, so it will automatically pick up our new table information. -=head2 Sanity-Check Reload of Development Server +=head2 Sanity-Check of the Development Server Reload -We aren't ready to try out the authentication just yet; we only want -to do a quick check to be sure our model loads correctly. Press -C to kill the previous server instance (if it's still running) -and restart it: - - $ script/myapp_server.pl - -Look for the three new model objects in the startup debug output: +We aren't ready to try out the authentication just yet; we only want to +do a quick check to be sure our model loads correctly. Assuming that you +are following along and using the "-r" option on C, +then the development server should automatically reload (if not, press +C to break out of the server if it's running and then enter +C