From dd694c44f48ee544a53851f619ed131b05ff25fd Mon Sep 17 00:00:00 2001 From: Jonathan Ellis Date: Sun, 21 Jan 2007 16:57:00 +0000 Subject: [PATCH] selectby -> select_by --- doc/build/content/datamapping.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/content/datamapping.txt b/doc/build/content/datamapping.txt index 68a17bea90..ba70e05a08 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. -- 2.47.2