firebird/firebird-mirror
firebird/firebird-mirror
8
0
Fork 1
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-02-01 12:43:03 +01:00
Code Issues
7e020184d0
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. */
Full domain support and NOT NULL in PSQL
2007-01-17 02:19:01 +01:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2007-01-09 22:43:00', 'JRD', 0, 560);
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
*/
1) CORE-645 and CORE-745: Database triggers 2) CORE-711: Make syntax for "CREATE TRIGGER" compliant with SQL2003
2006-11-05 19:30:36 +01:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2005-11-05 13:09:00', 'DSQL', 7, 32);
Fixed untracked collation dependencies in PSQL
2006-10-02 00:09:05 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-10-01 19:10:51', 'DYN', 8, 244);
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);
Misc
2006-11-06 02:07:31 +01:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-11-05 23:19:03', 'GBAK', 12, 295);
Replace few hardcoded error messages by new error codes
2006-11-05 11:54:46 +01:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-11-05 11:20:00', 'SQLERR', 13, 947);
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);
Solve three problems with arrays: - Don't allow to apply scalar/subscript syntax to fields that aren't array. - Detect if we get corrupt database containing array with more than 16 dimensions. - Reject attempt to subscript array with more than 16 dimensions and thus fix the buffer overrun.
2006-09-10 11:05:40 +02:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-09-10 03:04:31', 'JRD_BUGCHK', 15, 307);
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
*/
Please play by the rules: - New messages go at the end - Platform is named Windows (not windows or window) - Update facilities.sql accordingly.
2006-12-17 10:06:46 +01:00
INSERT INTO FACILITIES (LAST_CHANGE, FACILITY, FAC_CODE, MAX_NUMBER) VALUES ('2006-12-15 03:51:39', 'ISQL', 17, 156);
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