summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonathan Ellis <jbellis@gmail.com>2007-01-21 16:57:00 +0000
committerJonathan Ellis <jbellis@gmail.com>2007-01-21 16:57:00 +0000
commitdd694c44f48ee544a53851f619ed131b05ff25fd (patch)
treeaeb6e2e4692947635a21bdfa19d4f6ff535451b0
parent99924c8645be5cdaef35c26fabafb6605ca4482b (diff)
downloadsqlalchemy-dd694c44f48ee544a53851f619ed131b05ff25fd.tar.gz
selectby -> select_by
-rw-r--r--doc/build/content/datamapping.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/content/datamapping.txt b/doc/build/content/datamapping.txt
index 68a17bea9..ba70e05a0 100644
--- a/doc/build/content/datamapping.txt
+++ b/doc/build/content/datamapping.txt
@@ -446,7 +446,7 @@ Another way to specify joins more explicitly is to use the `from_obj` parameter
In the above example, the `join` function by default creates a natural join between the two tables, so we were able to avoid having to specify the join condition between `users` and `addresses` explicitly.
-#### Creating Joins Using selectby() {@name=relselectby}
+#### Creating Joins Using select\_by() {@name=relselectby}
Another way that joins can be created is by using the `select_by` method of `Query`, which has the ability to create joins across relationships automatically. This method is in many circumstances more convenient than, but not as flexible as, the more SQL-level approach using the `select()` method described in the previous section.