Reverted accidental 'svk pull' from inside mirrored checkout.

[dbsrgits/DBIx-Class.git] / lib / DBIx / Class / Manual / FAQ.pod

diff --git a/lib/DBIx/Class/Manual/FAQ.pod b/lib/DBIx/Class/Manual/FAQ.pod
index a76ccca..928808c 100644 (file)
--- a/lib/DBIx/Class/Manual/FAQ.pod
+++ b/lib/DBIx/Class/Manual/FAQ.pod
@@ -255,17 +255,6 @@ Call C<get_column> on a L<DBIx::Class::ResultSet>, this returns a
 L<DBIx::Class::ResultSetColumn>, see it's documentation and the
 L<Cookbook|DBIx::Class::Manual::Cookbook> for details.
 
-=item .. fetch a formatted column?
-
-In your table schema class, create a "private" column accessor with:
-
-  __PACKAGE__->add_columns(my_common => { accessor => '_hidden_my_column' });
-
-Then, in the same class, implement a subroutine called "my_column" that
-fetches the real value and does the formatting you want.
-
-See the Cookbook for more details.
-
 =back
 
 =head2 Inserting and updating data
@@ -307,35 +296,6 @@ scalar reference:
 
  ->update({ somecolumn => \'othercolumn' })
 
-=item .. store JSON/YAML in a column and have it deflate/inflate automatically?
-
-You can use L<DBIx::Class::InflateColumn> to accomplish YAML/JSON storage transparently.
-
-If you want to use JSON, then in your table schema class, do the following:
-
- use JSON;
-
- __PACKAGE__->add_columns(qw/ ... my_column ../)
- __PACKAGE__->inflate_column('my_column', {
-     inflate => sub { jsonToObj(shift) },
-     deflate => sub { objToJson(shift) },
- });
-
-For YAML, in your table schema class, do the following:
-
- use YAML;
-
- __PACKAGE__->add_columns(qw/ ... my_column ../)
- __PACKAGE__->inflate_column('my_column', {
-     inflate => sub { YAML::Load(shift) },
-     deflate => sub { YAML::Dump(shift) },
- });
-
-This technique is an easy way to store supplemental unstructured data in a table. Be
-careful not to overuse this capability, however. If you find yourself depending more
-and more on some data within the inflated column, then it may be time to factor that
-data out.
-
 =back
 
 =head2 Misc
@@ -357,7 +317,7 @@ to work around this issue.
 
 =item See the SQL statements my code is producing?
 
-Turn on debugging! See L<DBIx::Class::Storage::DBI> for details of how
+Turn on debugging! See L<DBIx::Class::Storage> for details of how
 to turn on debugging in the environment, pass your own filehandle to
 save debug to, or create your own callback.