Commit 3d5e2e86 authored by marko's avatar marko

branches/zip: Replace <number> with NUMBER in some comments,

to avoid problems with Doxygen XML output.
parent 7aead512
...@@ -1379,7 +1379,7 @@ dict_create_add_foreign_field_to_dictionary( ...@@ -1379,7 +1379,7 @@ dict_create_add_foreign_field_to_dictionary(
Add a single foreign key definition to the data dictionary tables in the Add a single foreign key definition to the data dictionary tables in the
database. We also generate names to constraints that were not named by the database. We also generate names to constraints that were not named by the
user. A generated constraint has a name of the format user. A generated constraint has a name of the format
databasename/tablename_ibfk_<number>, where the numbers start from 1, and databasename/tablename_ibfk_NUMBER, where the numbers start from 1, and
are given locally for this table, that is, the number is not global, as in are given locally for this table, that is, the number is not global, as in
the old format constraints < 4.0.18 it used to be. the old format constraints < 4.0.18 it used to be.
@return error code or DB_SUCCESS */ @return error code or DB_SUCCESS */
......
...@@ -110,7 +110,7 @@ dict_create_or_check_foreign_constraint_tables(void); ...@@ -110,7 +110,7 @@ dict_create_or_check_foreign_constraint_tables(void);
Adds foreign key definitions to data dictionary tables in the database. We Adds foreign key definitions to data dictionary tables in the database. We
look at table->foreign_list, and also generate names to constraints that were look at table->foreign_list, and also generate names to constraints that were
not named by the user. A generated constraint has a name of the format not named by the user. A generated constraint has a name of the format
databasename/tablename_ibfk_<number>, where the numbers start from 1, and are databasename/tablename_ibfk_NUMBER, where the numbers start from 1, and are
given locally for this table, that is, the number is not global, as in the given locally for this table, that is, the number is not global, as in the
old format constraints < 4.0.18 it used to be. old format constraints < 4.0.18 it used to be.
@return error code or DB_SUCCESS */ @return error code or DB_SUCCESS */
......
...@@ -3590,7 +3590,7 @@ row_delete_constraint( ...@@ -3590,7 +3590,7 @@ row_delete_constraint(
if ((err == DB_SUCCESS) && !strchr(id, '/')) { if ((err == DB_SUCCESS) && !strchr(id, '/')) {
/* Old format < 4.0.18 constraints have constraint ids /* Old format < 4.0.18 constraints have constraint ids
<number>_<number>. We only try deleting them if the NUMBER_NUMBER. We only try deleting them if the
constraint name does not contain a '/' character, otherwise constraint name does not contain a '/' character, otherwise
deleting a new format constraint named 'foo/bar' from deleting a new format constraint named 'foo/bar' from
database 'baz' would remove constraint 'bar' from database database 'baz' would remove constraint 'bar' from database
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment