From: Jess Robinson <castaway@desert-island.me.uk>
Date: Sun, 16 Jul 2006 13:23:15 +0000 (+0000)
Subject: More docs
X-Git-Tag: v0.07002~75^2~8
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=f7a90adc1a7f6ecbb940947deb461f0e91a993eb;p=dbsrgits%2FDBIx-Class.git

More docs
---

diff --git a/lib/DBIx/Class/Manual/FAQ.pod b/lib/DBIx/Class/Manual/FAQ.pod
index 477c011..392781e 100644
--- a/lib/DBIx/Class/Manual/FAQ.pod
+++ b/lib/DBIx/Class/Manual/FAQ.pod
@@ -206,8 +206,10 @@ for the join used by each relationship.
 =item .. create joins with conditions other than column equality?
 
 Currently, L<DBIx::Class> can only create join conditions using
-equality, so you're probably better off creating a VIEW in your
-database, and using that as your source.
+equality, so you're probably better off creating a C<view> in your
+database, and using that as your source. A C<view> is a stored SQL query,
+which can be accessed similarly to a table, see your database
+documentation for details.
 
 =item .. search using greater-than or less-than and database functions?
 
@@ -290,7 +292,7 @@ scalar reference:
 
 You can add your own data accessors to your classes.
 
-=item How do I use DBIx::Class objects my TT templates?
+=item How do I use DBIx::Class objects in my TT templates?
 
 Like normal objects, mostly. However you need to watch out for TTs
 calling methods in list context, this means that when calling
@@ -299,7 +301,9 @@ the related objects.
 
 =item See the SQL statements my code is producing?
 
-Turn on debugging!
+Turn on debugging! See L<DBIx::Class::Storage::DBI> for details of how
+to turn on debugging in the environment, pass your own filehandle to
+save debug to, or create your own callback.
 
 =item Why didn't my search run any SQL?
 
diff --git a/lib/DBIx/Class/Storage/DBI.pm b/lib/DBIx/Class/Storage/DBI.pm
index d5c34c7..c485257 100644
--- a/lib/DBIx/Class/Storage/DBI.pm
+++ b/lib/DBIx/Class/Storage/DBI.pm
@@ -417,6 +417,9 @@ This method is deprecated in favor of setting via L</connect_info>.
 Causes SQL trace information to be emitted on the C<debugobj> object.
 (or C<STDERR> if C<debugobj> has not specifically been set).
 
+This is the equivalent to setting L</DBIC_TRACE> in your
+shell environment.
+
 =head2 debugfh
 
 Set or retrieve the filehandle used for trace/debug output.  This should be