[Firebird-devel] Error messages how-to
Hello, All. Is there a simple step-by-step guide how to add new error codes and corresponding messages into the engine and firebird.msg? -- WBR, SD. -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
12.08.2014 15:51, Dmitry Yemanov wrote: 1) Choose the facility for your error How to choose between JRD and DSQL? -- WBR, SD. -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
On Tue, 12 Aug 2014 17:51:36 +0400, Dmitry Yemanov firebi...@yandex.ru wrote: 12.08.2014 17:34, Dimitry Sibiryakov wrote: Is there a simple step-by-step guide how to add new error codes and corresponding messages into the engine and firebird.msg? 1) Choose the facility for your error 2) Bump next error number in facilities.sql for your facility 3) Add a record into /system_errors.sql at the tail (for your facility) 4) Add a record into messages.sql at the tail (for your facility) 5) Rebuild then optionally: 6) Use the new error code 7) Rebuild Doesn't this miss a add specific standard (or vendor-specific) SQL state somewhere? Mark -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
12.08.2014 18:03, Mark Rotteveel wrote: Doesn't this miss a add specific standard (or vendor-specific) SQL state somewhere? It's hidden inside item (3) ;-) Dmitry -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
Sigh. There used to be database based system to create and edit messages and generate header and message files. Very handy using a database to develop a database system. On Aug 12, 2014, at 9:34 AM, Dimitry Sibiryakov s...@ibphoenix.com wrote: Hello, All. Is there a simple step-by-step guide how to add new error codes and corresponding messages into the engine and firebird.msg? -- WBR, SD. -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
12.08.2014 18:17, Jim Starkey wrote: There used to be database based system to create and edit messages and generate header and message files. Yes, I know that because I am exactly that guy who killed this system because database isn't suitable for CVS. -- WBR, SD. -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
On Aug 12, 2014, at 1:17 PM, Jim Starkey j...@jimstarkey.net wrote: Sigh. There used to be database based system to create and edit messages and generate header and message files. Very handy using a database to develop a database system. Please lets not get into the moral and political issues of recursive development tools! That discussion makes the API questions look reasonable and productive. Yours for peace and harmony, Ann -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
Hi Dimitry, May I ask why you say a database system is not suitable for CVS? I had ours on cvs for a few years before moving it to git. If you view the operational database as source code, then I can understand your point, but, I view an operational database as a compiled end product while the DDL/DML is the source code that has version control applied to it. A standardised DDL/DML extraction tool is all you need. Very simple to setup, very simple to apply the finished product to a database. Part of a standardised build process, of creating and populating a sand box database via scripts, is very easy to setup. I am just trying to understand where you are coming from as this has always been possible from the days of interbase. best regards Dalton On 12 August 2014 12:25, Dimitry Sibiryakov s...@ibphoenix.com wrote: 12.08.2014 18:17, Jim Starkey wrote: There used to be database based system to create and edit messages and generate header and message files. Yes, I know that because I am exactly that guy who killed this system because database isn't suitable for CVS. -- WBR, SD. -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
On 12-8-2014 19:22, Dalton Calford wrote: May I ask why you say a database system is not suitable for CVS? I had ours on cvs for a few years before moving it to git. If you view the operational database as source code, then I can understand your point, but, I view an operational database as a compiled end product while the DDL/DML is the source code that has version control applied to it. A standardised DDL/DML extraction tool is all you need. Very simple to setup, very simple to apply the finished product to a database. Part of a standardised build process, of creating and populating a sand box database via scripts, is very easy to setup. I am just trying to understand where you are coming from as this has always been possible from the days of interbase. I think you misunderstand. Historically, the error messages within the build where stored inside a Firebird database. That database itself was the source for the generated header with errorcodes and the firebird.msg file. CVS has its share of problems with storing binary files (although that isn't really relevant anymore as the project doesn't use CVS anymore for Firebird core). Second - and IMHO more important - not being able to (easily) diff or merge changes with a binary file where you can with a text file (or: sql script). Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
Hi Mark, If I understand your message, I am still confused by the statement. I would never, ever put a binary such as a database or compiled executable into a version control system, but, there is nothing preventing my extracting the DML (insert into foo .values..) and inserting that into the version control system. If the error messages are binary blobs, then I could see the problem, but if they where text, it should work, easily be merged etc. I perform Diff's and merges with DDL and DML almost every day. best regards Dalton On 12 August 2014 13:31, Mark Rotteveel m...@lawinegevaar.nl wrote: On 12-8-2014 19:22, Dalton Calford wrote: May I ask why you say a database system is not suitable for CVS? I had ours on cvs for a few years before moving it to git. If you view the operational database as source code, then I can understand your point, but, I view an operational database as a compiled end product while the DDL/DML is the source code that has version control applied to it. A standardised DDL/DML extraction tool is all you need. Very simple to setup, very simple to apply the finished product to a database. Part of a standardised build process, of creating and populating a sand box database via scripts, is very easy to setup. I am just trying to understand where you are coming from as this has always been possible from the days of interbase. I think you misunderstand. Historically, the error messages within the build where stored inside a Firebird database. That database itself was the source for the generated header with errorcodes and the firebird.msg file. CVS has its share of problems with storing binary files (although that isn't really relevant anymore as the project doesn't use CVS anymore for Firebird core). Second - and IMHO more important - not being able to (easily) diff or merge changes with a binary file where you can with a text file (or: sql script). Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
On 12-8-2014 19:37, Dalton Calford wrote: If I understand your message, I am still confused by the statement. I would never, ever put a binary such as a database or compiled executable into a version control system, but, there is nothing preventing my extracting the DML (insert into foo .values..) and inserting that into the version control system. If the error messages are binary blobs, then I could see the problem, but if they where text, it should work, easily be merged etc. I perform Diff's and merges with DDL and DML almost every day. That is exactly how it works now, see: http://sourceforge.net/p/firebird/code/HEAD/tree/firebird/trunk/src/msgs/ Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Error messages how-to
12.08.2014 19:37, Dalton Calford wrote: I would never, ever put a binary such as a database or compiled executable into a version control system, but, there is nothing preventing my extracting the DML (insert into foo .values..) and inserting that into the version control system. And it was exactly what I did. Unfortunately handy utility like add_message and modify_message become useless. Now messages have to be added to the scripts by hand. -- WBR, SD. -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
