After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701498 - Broken "gen:" link to chapter in reference documentation
Broken "gen:" link to chapter in reference documentation
Status: RESOLVED DUPLICATE of bug 699406
Product: libgda
Classification: Other
Component: Documentation
unspecified
Other All
: Normal normal
: ---
Assigned To: malerba
malerba
Depends on:
Blocks:
 
 
Reported: 2013-06-03 08:48 UTC by Simon Kågedal
Modified: 2014-04-27 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Simon Kågedal 2013-06-03 08:48:43 UTC 
From both https://developer.gnome.org/libgda/5.0/ and https://developer.gnome.org/libgda/5.1/ there is a link to a chapter called "SQL identifiers" that has the peculiar URL "gen:sql_identifiers.html".  It's the same from other places such as https://developer.gnome.org/libgda/5.0/ch04.html and the next link from https://developer.gnome.org/libgda/5.0/null_handling.html .
Comment 1 André Klapper 2014-01-25 21:54:33 UTC 
Confirming.

./libgda/gda-meta-store.c: * identifiers naming convention, see the <link linkend="gen:sql_identifiers">SQL identifiers</link>
./libgda/gda-util.c: * For more information, see the <link linkend="gen:sql_identifiers">SQL identifiers and abstraction</link> and
./libgda/Gda-5.0.gir:identifiers naming convention, see the &lt;link linkend="gen:sql_identifiers"&gt;SQL identifiers&lt;/link&gt;
./libgda/Gda-5.0.gir:For more information, see the &lt;link linkend="gen:sql_identifiers"&gt;SQL identifiers and abstraction&lt;/link&gt; and
./doc/C/libgda-5.0-docs.sgml:	    Please refer to the <link linkend="gen:sql_identifiers">SQL identifiers and abstraction</link> section
Comment 2 Murray Cumming 2014-04-27 14:17:51 UTC 
Hopefully this has been fully fixed but the patch in bug #699406 .

*** This bug has been marked as a duplicate of bug 699406 ***