[Firebird-devel] [FB-Tracker] Created: (CORE-6471) Add MON$ELAPSED_TIME to MON$STATEMENTS
Add MON$ELAPSED_TIME to MON$STATEMENTS -- Key: CORE-6471 URL: http://tracker.firebirdsql.org/browse/CORE-6471 Project: Firebird Core Issue Type: New Feature Components: Engine Reporter: Karol Bieniaszewski Add cumulative time during query execution. Query can be be stalled and active back in long intervals but it can be relative short as a whole. Look at discussion with Vlad Khorsun in CORE-6456 maybe you find more fields/statistics to add. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-6470) Provide ability to suppress localized messages in error stack (or make them to be encoded to required charset, say 'utf8')
Provide ability to suppress localized messages in error stack (or make them to be encoded to required charset, say 'utf8') -- Key: CORE-6470 URL: http://tracker.firebirdsql.org/browse/CORE-6470 Project: Firebird Core Issue Type: Improvement Reporter: Pavel Zotov Attachments: file-related-error-messages-in-localized-form.png I can't understand for what reason FB utilities issue part of error messages in localized form. Please provide ability either to fully supress such messages or make them be displayed in apropriate encoding, which must be equal to connection charset. Please look: C:\HQBWork\1IMPORTANT\QA-rundaily>chcp Active code page: 65001 C:\HQBWork\1IMPORTANT\QA-rundaily>echo set names utf8; create database 'z:\nosuch_disk\no_such_folder\foo.fdb' user sysdba password 'masterkey'; | isql -q 1>isql-stdout.log 2>isql-stderr.log C:\HQBWork\1IMPORTANT\QA-rundaily>type isql-stderr.log Statement failed, SQLSTATE = 08006 Unable to complete network request to host "z". -Failed to locate host machine. -The specified name was not found in the hosts file or Domain Name Services. // here we see all messages in ascii (good). C:\HQBWork\1IMPORTANT\QA-rundaily>echo set names utf8; create database 'c:\no_such_folder\foo.fdb' user sysdba password 'masterkey'; | isql -q 1>isql-stdout.log 2>isql-stderr.log C:\HQBWork\1IMPORTANT\QA-rundaily>type isql-stderr.log Statement failed, SQLSTATE = 08001 I/O error during "CreateFile (create)" operation for file "C:\NO_SUCH_FOLDER\FOO.FDB" -Error while trying to create file -��� �� ��� � � . // here we can not read last line C:\HQBWork\1IMPORTANT\QA-rundaily>chcp 1251 Active code page: 1251 C:\HQBWork\1IMPORTANT\QA-rundaily>type isql-stderr.log Statement failed, SQLSTATE = 08001 I/O error during "CreateFile (create)" operation for file "C:\NO_SUCH_FOLDER\FOO.FDB" -Error while trying to create file -Системе не удается найти указанный путь. // here we *can* read last line but we have to change code page to that Windows uses. I can not imagine FB admin who will not be able to translate from english messages related to file/process access. Or at least to use goodle translate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$CONFIG.RDB$CONFIG_NAME datatype
20.01.2021 15:43, Adriano dos Santos Fernandes wrote: On 20/01/2021 10:03, Alex Peshkoff via Firebird-devel wrote: I suppose VARCHAR(63) CHARACTER SET ASCII is OK. I agree. Seems, we have agreement, very well. Thanks all, Vlad Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$CONFIG.RDB$CONFIG_NAME datatype
On 20/01/2021 10:03, Alex Peshkoff via Firebird-devel wrote: > > I suppose VARCHAR(63) CHARACTER SET ASCII is OK. > I agree. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$CONFIG.RDB$CONFIG_NAME datatype
20.01.2021 16:03, Dimitry Sibiryakov wrote: I agree that config parameters hardly can be not in ASCII but I cannot imagine them to be longer that 10-20 characters. It would be very hard to type such long settings without errors and my imagination is not enough to suggest a meaningful name of such length. Not all people are that lazy in typing, recalling a request to increase our metadata names length up from 31 chars ;-) But basically I agree. Our longest config setting has 30 chars in length and it looks cumbersome. So having some limit makes sense to ensure readability and thus I'm against raising it even more. Personally, I don't care whether this limit is 30 or 50 or 63. I don't see good reasons to have it bound to metadata names length, but on the other side -- why not. And +1 for ASCII. Dmitry Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$CONFIG.RDB$CONFIG_NAME datatype
20.01.2021 13:41, Vlad Khorsun wrote: Today we discussed these reasons with Dmitry and agreed that it is not very convincing. For example, we have no intention to have non-ASCII names of settings in firebird.conf and 63 characters could be not enough at some day. I agree that config parameters hardly can be not in ASCII but I cannot imagine them to be longer that 10-20 characters. It would be very hard to type such long settings without errors and my imagination is not enough to suggest a meaningful name of such length. -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] RDB$CONFIG.RDB$CONFIG_NAME datatype
On 1/20/21 3:41 PM, Vlad Khorsun wrote: Hi, all I'll speak about new table RDB$CONFIG introduced with implementation of CORE-3708. The field RDB$CONFIG_NAME has datatype defined as VARCHAR(63) CHARACTER SET UTF8. The original reasons behind this choice was: - UTF8 as charset for most system defined fields, - VARCHAR(63) to not occupy too much space and to be compatible with SQL identifier max length. Today we discussed these reasons with Dmitry and agreed that it is not very convincing. For example, we have no intention to have non-ASCII names of settings in firebird.conf and 63 characters could be not enough at some day. So, the question is - should be change this definition and, if yes, what it should be ? I can think about VARCHAR(255) CHARACTER SET ASCII, for example. More opinions ? 63 symbols not enough for configuration parameter name? You are kidding :-) I suppose VARCHAR(63) CHARACTER SET ASCII is OK. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] RDB$CONFIG.RDB$CONFIG_NAME datatype
Hi, all I'll speak about new table RDB$CONFIG introduced with implementation of CORE-3708. The field RDB$CONFIG_NAME has datatype defined as VARCHAR(63) CHARACTER SET UTF8. The original reasons behind this choice was: - UTF8 as charset for most system defined fields, - VARCHAR(63) to not occupy too much space and to be compatible with SQL identifier max length. Today we discussed these reasons with Dmitry and agreed that it is not very convincing. For example, we have no intention to have non-ASCII names of settings in firebird.conf and 63 characters could be not enough at some day. So, the question is - should be change this definition and, if yes, what it should be ? I can think about VARCHAR(255) CHARACTER SET ASCII, for example. More opinions ? Regards, Vlad Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
