Re: [Firebird-devel] Service errors returned by API
Alex Peshkoff via Firebird-devel wrote 25.08.2022 10:27: But here are some problems: - An error when querying service is treated by 99% of callers (starting with fbsvcmgr) as fatal one. Other errors will not be displayed. And it is the right way to handle them, IMHO. - What about warnings - yes, they probably may be used at the first glance. But once again big problems with old clients. What should return isc_service_query - success or failure? On failure one prints status and detachs from service, on success - ignores SV. Wasn't it always the way warnings were working: success in function result and requirement to parse vector to get them?.. Perhaps warnings should be returned both ways: the binary form in status and duplicate text in output. In this case applications will get them as usual and advanced ones may be interested in parsing status. - Verbose messages are already passed through isc_svc_query(). That's what they belongs to. Certainly we may require analyzing warnings from clients who want to receive verbose messages in machine-readable form. Is it what you want? Rather no. As written above - messages belong to (one of) output streams (I believe services API should be able to deliver multiple streams in parallel: messages and binary stream for backup as an example). -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
> As the Intel platforms will be the *huge* majority, what about this: > > win32 | win64 |win64-arm > > or this: > > win32-x86 | win64-x86 | win64-arm > > or just: > > win32 | win64-x86 | win64-arm That seems pretty inconsistent (in regards to other filenames). -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25-08-2022 15:13, Stefan Heymann wrote: I propose this name convention starting with Firebird 5: Firebird-5.0.0.2816-0-windows-x86-pdb.exe Firebird-5.0.0.2816-0-windows-x86-pdb.zip Firebird-5.0.0.2816-0-windows-x86.exe Firebird-5.0.0.2816-0-windows-x86.zip Firebird-5.0.0.2816-0-windows-x64-pdb.exe Firebird-5.0.0.2816-0-windows-x64-pdb.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip [...] I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it you want to keep the "windows" prefix, use window-32 and windows-64. For me as a Windows user this would be much more logical (the 86 comes from the 80*86 processor, the 64 comes from 64 bits, so it's not consistent from the beginning). The proposed naming has the benefit it is consistent across platforms. That is: Firebird---[-qualifier]. I don't see the need, nor the point to deviate from this for Windows. Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
>> > I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it >> > you want to keep the "windows" prefix, use window-32 and windows-64. >> > For me as a Windows user this would be much more logical (the 86 comes >> > from the 80*86 processor, the 64 comes from 64 bits, so it's not >> > consistent from the beginning). > In the past win32 and win64 was good but now Windows exists for ARM64. > x86, x(86-)64, arm64, etc. are more clear. But I am not a core developer just > a user. :-) As the Intel platforms will be the *huge* majority, what about this: win32 | win64 |win64-arm or this: win32-x86 | win64-x86 | win64-arm or just: win32 | win64-x86 | win64-arm Regards Stefan Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
> In the past win32 and win64 was good but now Windows exists for ARM64. > x86, x(86-)64, arm64, etc. are more clear. But I am not a core developer > just a user. :-) Same for me. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
2022.08.25. 15:13 keltezéssel, Stefan Heymann írta: I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it you want to keep the "windows" prefix, use window-32 and windows-64. For me as a Windows user this would be much more logical (the 86 comes from the 80*86 processor, the 64 comes from 64 bits, so it's not consistent from the beginning). In the past win32 and win64 was good but now Windows exists for ARM64. x86, x(86-)64, arm64, etc. are more clear. But I am not a core developer just a user. :-) Gabor Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
> I propose this name convention starting with Firebird 5: > Firebird-5.0.0.2816-0-windows-x86-pdb.exe > Firebird-5.0.0.2816-0-windows-x86-pdb.zip > Firebird-5.0.0.2816-0-windows-x86.exe > Firebird-5.0.0.2816-0-windows-x86.zip > Firebird-5.0.0.2816-0-windows-x64-pdb.exe > Firebird-5.0.0.2816-0-windows-x64-pdb.zip > Firebird-5.0.0.2816-0-windows-x64.exe > Firebird-5.0.0.2816-0-windows-x64.zip > [...] I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it you want to keep the "windows" prefix, use window-32 and windows-64. For me as a Windows user this would be much more logical (the 86 comes from the 80*86 processor, the 64 comes from 64 bits, so it's not consistent from the beginning). Best Regards Stefan -- Stefan Heymann, Tübingen, Germany Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25-08-2022 12:38, Dimitry Sibiryakov wrote: Dmitry Yemanov wrote 25.08.2022 12:34: Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x86.exe Firebird-5.0.0.2816-0-windows-x86.zip Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip Firebird-5.0.0.2816-0-linux-x64.tar.gz Firebird-5.0.0.2816-0-linux-x64-debugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm.tar.gz (armv7, other?) Firebird-5.0.0.2816-0-android-arm-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm64.tar.gz Firebird-5.0.0.2816-0-android-arm64-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-linux-x86.tar.gz Firebird-5.0.0.2816-0-linux-x86-debugSymbols.tar.gz Firebird-5.0.0.2816-0-source.tar.xz Firebird-5.0.0.2816-0-macos-x64.pkg Looks good to me. Is this zero after build number necessary? We have had -1 releases, e.g. https://firebirdsql.org/en/firebird-4-0-0/#Win32 (Firebird-4.0.0.2496-1-Win32.exe), so for consistency, either it should always be included, or we should ditch this package revision (or whatever we should call it) entirely. Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25/08/2022 07:38, Dimitry Sibiryakov wrote: > > Is this zero after build number necessary? > It's packaging number. We had this type of problem in Windows build in the past, where retag was not necessary and the package number was increased. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25/08/2022 07:19, Mark Rotteveel wrote: > On 25-08-2022 03:15, Adriano dos Santos Fernandes wrote: >> On 24/08/2022 08:45, Adriano dos Santos Fernandes wrote: >>> >>> I propose this name convention starting with Firebird 5: >>> >> >> Here is my updated proposal based on the discussion so far: >> >> Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.exe >> Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.zip >> Firebird-5.0.0.2816-0-windows-x86.exe >> Firebird-5.0.0.2816-0-windows-x86.zip >> Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.exe >> Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.zip >> Firebird-5.0.0.2816-0-windows-x64.exe >> Firebird-5.0.0.2816-0-windows-x64.zip >> Firebird-5.0.0.2816-0-linux-x64.tar.gz >> Firebird-5.0.0.2816-0-linux-x64-debugSymbols.tar.gz >> Firebird-5.0.0.2816-0-android-arm.tar.gz (armv7, other?) >> Firebird-5.0.0.2816-0-android-arm-withDebugSymbols.tar.gz >> Firebird-5.0.0.2816-0-android-arm64.tar.gz >> Firebird-5.0.0.2816-0-android-arm64-withDebugSymbols.tar.gz >> Firebird-5.0.0.2816-0-linux-x86.tar.gz >> Firebird-5.0.0.2816-0-linux-x86-debugSymbols.tar.gz >> Firebird-5.0.0.2816-0-source.tar.xz >> Firebird-5.0.0.2816-0-macos-x64.pkg > > Sounds OK. On suggestion: use "with-debug-symbols" and "debug-symbols", > but that is just because I'm a bit allergic to capitals in filenames ;) > Me too, but I want to use dashes to separate components in this case, and then it would be inconsistent have a single information spread into multiple parts. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
Dmitry Yemanov wrote 25.08.2022 12:34: Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x86.exe Firebird-5.0.0.2816-0-windows-x86.zip Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip Firebird-5.0.0.2816-0-linux-x64.tar.gz Firebird-5.0.0.2816-0-linux-x64-debugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm.tar.gz (armv7, other?) Firebird-5.0.0.2816-0-android-arm-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm64.tar.gz Firebird-5.0.0.2816-0-android-arm64-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-linux-x86.tar.gz Firebird-5.0.0.2816-0-linux-x86-debugSymbols.tar.gz Firebird-5.0.0.2816-0-source.tar.xz Firebird-5.0.0.2816-0-macos-x64.pkg Looks good to me. Is this zero after build number necessary? -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
25.08.2022 04:15, Adriano dos Santos Fernandes wrote: Here is my updated proposal based on the discussion so far: Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x86.exe Firebird-5.0.0.2816-0-windows-x86.zip Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip Firebird-5.0.0.2816-0-linux-x64.tar.gz Firebird-5.0.0.2816-0-linux-x64-debugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm.tar.gz (armv7, other?) Firebird-5.0.0.2816-0-android-arm-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm64.tar.gz Firebird-5.0.0.2816-0-android-arm64-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-linux-x86.tar.gz Firebird-5.0.0.2816-0-linux-x86-debugSymbols.tar.gz Firebird-5.0.0.2816-0-source.tar.xz Firebird-5.0.0.2816-0-macos-x64.pkg Looks good to me. Dmitry Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25-08-2022 03:15, Adriano dos Santos Fernandes wrote: On 24/08/2022 08:45, Adriano dos Santos Fernandes wrote: I propose this name convention starting with Firebird 5: Here is my updated proposal based on the discussion so far: Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x86.exe Firebird-5.0.0.2816-0-windows-x86.zip Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip Firebird-5.0.0.2816-0-linux-x64.tar.gz Firebird-5.0.0.2816-0-linux-x64-debugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm.tar.gz (armv7, other?) Firebird-5.0.0.2816-0-android-arm-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm64.tar.gz Firebird-5.0.0.2816-0-android-arm64-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-linux-x86.tar.gz Firebird-5.0.0.2816-0-linux-x86-debugSymbols.tar.gz Firebird-5.0.0.2816-0-source.tar.xz Firebird-5.0.0.2816-0-macos-x64.pkg Sounds OK. On suggestion: use "with-debug-symbols" and "debug-symbols", but that is just because I'm a bit allergic to capitals in filenames ;) Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Service errors returned by API (was: [FirebirdSQL/firebird] [FR] Database restore must make every effort on activating deferred indexes (Issue #7269))
On 8/24/22 20:59, Dimitry Sibiryakov wrote: Alexander Peshkov wrote 24.08.2022 19:06: On 8/24/22 14:31, Dimitry Sibiryakov wrote: > Without it services seem to be pretty useless. I think this to be suggested in devel and if nobody sees problems - feel free to add a ticket, I will implement it. Ok. But I don't think that a simple hack returning only thread exit code is a right way to go. If I was thinking that way that feature could be present since 2. 5 :-) Notice - in status vector it will be a notice that service thread failed with exit code NNN, original message with a reason for is unknown at the final point. It is not quite try. In the old dark days when the service thread just run an external utility and mindlessly redirect whole output to the client it was so. But nowadays the thread is doing whole work itself Just small notice - an ability to return errors in SV does not directly depend upon does service run as a process or as a thread. It's possible to pass SV cross-process but nobody cared about. With service threads pre-2.5 it was a mix - some errors were returned as SV, some - as text lines. so it can return a proper errors, warnings and verbose messages through isc_svc_query() as soon as they happen. But here are some problems: - An error when querying service is treated by 99% of callers (starting with fbsvcmgr) as fatal one. Other errors will not be displayed. - What about warnings - yes, they probably may be used at the first glance. But once again big problems with old clients. What should return isc_service_query - success or failure? On failure one prints status and detachs from service, on success - ignores SV. - Verbose messages are already passed through isc_svc_query(). Certainly we may require analyzing warnings from clients who want to receive verbose messages in machine-readable form. Is it what you want? Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
