firebird/firebird-mirror
firebird/firebird-mirror
8
0
Fork 1
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-02-01 15:20:39 +01:00
Code Issues
f3b5317b62
firebird-mirror/src/msgs/facilities.sql

33 lines
2.6 KiB
MySQL
Raw Normal View History

- Adjust error messages. - Correct way to stop automatically generated triggers from being altered.
2005-05-20 02:23:25 +02:00
/* MAX_NUMBER is the next number to be used, always one more than the highest message number. */
Allow usage of domains in PSQL (with TYPE OF syntax)
2006-08-19 04:52:39 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-08-18 22:35:00', 'JRD', 0, 553);
Archeology: enable QLI to handle NUMERIC, DECIMAL and BIGINT in definitions. No dialect check made.
2005-09-03 07:52:02 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2005-09-02 00:55:59', 'QLI', 1, 513);
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:38:37', 'GDEF', 2, 345);
Fixed misplaced error messages in gfix. For example, if you do gfix - housekeeping you were getting "dialect number required".
2005-07-31 03:06:20 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2005-07-20 04:04:04', 'GFIX', 3, 115);
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:39:40', 'GPRE', 4, 1);
The facilities's MAX_NUMBER is one more than the last used number in messages.sql for each facility. It worked nicely for years until the utilities became obsolete.
2004-11-19 04:50:19 +01:00
/*
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:39:40', 'GLTJ', 5, 1);
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:39:40', 'GRST', 6, 1);
The facilities's MAX_NUMBER is one more than the last used number in messages.sql for each facility. It worked nicely for years until the utilities became obsolete.
2004-11-19 04:50:19 +01:00
*/
Allow usage of domains in PSQL (with TYPE OF syntax)
2006-08-19 04:52:39 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2005-08-18 22:35:00', 'DSQL', 7, 26);
Fix two domain-related deletion messages; one of the fixes was taken from Bill Oliver's commit.
2006-08-31 10:24:56 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-08-31 04:21:42', 'DYN', 8, 240);
The facilities's MAX_NUMBER is one more than the last used number in messages.sql for each facility. It worked nicely for years until the utilities became obsolete.
2004-11-19 04:50:19 +01:00
/*
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:39:40', 'FRED', 9, 1);
The facilities's MAX_NUMBER is one more than the last used number in messages.sql for each facility. It worked nicely for years until the utilities became obsolete.
2004-11-19 04:50:19 +01:00
*/
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:39:40', 'INSTALL', 10, 1);
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:38:41', 'TEST', 11, 4);
1.- COALESCE/CASE and VIA (subqueries) allowed breach in computed field checks (no array and no blob). 2.- Misc: since gbak allows not only to backup metadata only but to restore metadata only (even from a full backup), changed the help message.
2006-07-30 04:59:29 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-07-28 06:38:03', 'GBAK', 12, 294);
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-07-28 19:58:33', 'SQLERR', 13, 925);
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:38:42', 'SQLWARN', 14, 102);
Replace one fb_assert with BUGCHECK as Claudio suggested some time ago
2006-02-03 17:57:26 +01:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-02-03 18:30:00', 'JRD_BUGCHK', 15, 306);
The facilities's MAX_NUMBER is one more than the last used number in messages.sql for each facility. It worked nicely for years until the utilities became obsolete.
2004-11-19 04:50:19 +01:00
/*
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1996-11-07 13:38:43', 'GJRN', 16, 241);
The facilities's MAX_NUMBER is one more than the last used number in messages.sql for each facility. It worked nicely for years until the utilities became obsolete.
2004-11-19 04:50:19 +01:00
*/
Implementation of CREATE/DROP COLLATION and ISQL show/extraction of collations
2006-08-07 18:39:21 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-08-07 13:00:00', 'ISQL', 17, 150);
Content of messages DB's FACILITIES table
2004-08-23 11:33:10 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('1998-11-04 11:06:15', 'GSEC', 18, 91);
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2002-03-05 02:30:12', 'LICENSE', 19, 60);
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2002-03-05 02:31:54', 'DOS', 20, 74);
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2001-10-10 18:05:16', 'GSTAT', 21, 36);
COMMIT WORK;
Fixed misplaced error messages in gfix. For example, if you do gfix - housekeeping you were getting "dialect number required".
2005-07-31 03:06:20 +02:00
Copy Permalink