diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2006-07-02 16:34:03 +0000 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2006-07-02 16:34:03 +0000 |
| commit | 433f20d631085cf0e14348b4055e45db080b630f (patch) | |
| tree | 4c7a441d9e9b554c64e47c015fbc5ee60fc37727 | |
| parent | 498d1b8dd8310f2d2dd18d11a9e6082e143f6cdc (diff) | |
| download | sqlalchemy-433f20d631085cf0e14348b4055e45db080b630f.tar.gz | |
fixed hyperlink to adv datamapping
| -rw-r--r-- | doc/build/content/tutorial.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/content/tutorial.txt b/doc/build/content/tutorial.txt index 44c5c2db1..80f2d4472 100644 --- a/doc/build/content/tutorial.txt +++ b/doc/build/content/tutorial.txt @@ -357,7 +357,7 @@ At the moment, nothing has been saved to the database; all of our changes are in With the identity map, a single `Session` can be relied upon to keep all loaded instances straight. -As far as the issue of the same object being modified in two different Sessions, that's an issue of concurrency detection; SQLAlchemy does some basic concurrency checks when saving objects, with the option for a stronger check using version ids. See [adv_datamapping](rel:adv_datamapping) for more details. +As far as the issue of the same object being modified in two different Sessions, that's an issue of concurrency detection; SQLAlchemy does some basic concurrency checks when saving objects, with the option for a stronger check using version ids. See [advdatamapping_arguments](rel:advdatamapping_arguments) for more details. ### Saving {@name=saving} |