X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FManual%2FFAQ.pod;h=114583df49054bfddd45a7affa862db54ddded27;hb=40f2550b1a00ae9f2ff993e7bef867adf73b8aff;hp=d6353427f9ab2a73178d348d0cd8907870cca83e;hpb=e416146eb60e344696702986dc8cf171314634d8;p=dbsrgits%2FDBIx-Class.git diff --git a/lib/DBIx/Class/Manual/FAQ.pod b/lib/DBIx/Class/Manual/FAQ.pod index d635342..114583d 100644 --- a/lib/DBIx/Class/Manual/FAQ.pod +++ b/lib/DBIx/Class/Manual/FAQ.pod @@ -87,7 +87,7 @@ as part of the name, and make sure you give the one user you are going to connect with rights to read/write all the schemas/tables as necessary. -=back +=back =head2 Relationships @@ -112,7 +112,7 @@ for details. Create a C relationship for the field containing the foreign key. See L. -=item .. define a foreign key relationship where the key field may contain NULL? +=item .. define a foreign key relationship where the key field may contain NULL? Just create a C relationship, as above. If the column is NULL then the inflation to the foreign object will not happen. This @@ -307,8 +307,8 @@ See the prefetch examples in the L. =item .. fetch a whole column of data instead of a row? -Call C on a L, this returns a -L, see it's documentation and the +Call C on a L. This returns a +L. See its documentation and the L for details. =item .. fetch a formatted column? @@ -410,17 +410,17 @@ scalar reference: But note that when using a scalar reference the column in the database will be updated but when you read the value from the object with e.g. - + ->somecolumn() - + you still get back the scalar reference to the string, B the new value in the database. To get that you must refresh the row from storage using C. Or chain your function calls like this: ->update->discard_changes - - to update the database and refresh the object in one step. - + +to update the database and refresh the object in one step. + =item .. store JSON/YAML in a column and have it deflate/inflate automatically? You can use L to accomplish YAML/JSON storage transparently. @@ -474,7 +474,7 @@ An another method is to use L with your L package. package MyTable; use Moose; # import Moose - use Moose::Util::TypeConstraint; # import Moose accessor type constraints + use Moose::Util::TypeConstraint; # import Moose accessor type constraints extends 'DBIx::Class'; # Moose changes the way we define our parent (base) package @@ -486,7 +486,7 @@ With either of these methods the resulting use of the accesssor would be my $row; - # assume that some where in here $row will get assigned to a MyTable row + # assume that somewhere in here $row will get assigned to a MyTable row $row->non_column_data('some string'); # would set the non_column_data accessor @@ -494,7 +494,7 @@ With either of these methods the resulting use of the accesssor would be $row->update(); # would not inline the non_column_data accessor into the update - + =item How do I use DBIx::Class objects in my TT templates? Like normal objects, mostly. However you need to watch out for TT @@ -536,7 +536,7 @@ Look at the tips in L =item How do I reduce the overhead of database queries? You can reduce the overhead of object creation within L -using the tips in L +using the tips in L and L =back