Re: [Firebird-devel] Roadmap, Planning Board, version of 4.0 snapshots

2022-08-16 Thread Gabor Boros
2022.03.04. 15:04 keltezéssel, Dmitry Yemanov írta: Updated, thanks. 4.0.2 already released but snapshot's version still 4.0.2. 5.0 Alpha not released in June, please update the Planning Board page. Gabor Firebird-Devel mailing list, web interface at

[Firebird-devel] Windows snapshor for Firebird 5.0

2022-08-16 Thread Simonov Denis via Firebird-devel
No snapshots for windows in http://web.firebirdsql.org/download/snapshot_builds/win/5.0/ And the second problem. If you download the artifact https://github.com/FirebirdSQL/firebird/suites/7826192155/artifacts/330779110 and others under Windows, it does not contain default_profiler.dll

Re: [Firebird-devel] Current value for parallel workers

2022-08-16 Thread Jiří Činčura
> I think DBA may want a monitoring table (MON$WORKERS?) that shows how > many workers are currently active, what attachment are they bound to, > and what task (backup/sweep/etc) are they used for. Maybe some other > metrics could be added later. Sounds good to me as well. -- Mgr. Jiří

Re: [Firebird-devel] New statement: EXECUTE SQL

2022-08-16 Thread Adriano dos Santos Fernandes
On Tue, Aug 16, 2022 at 3:48 AM Mark Rotteveel wrote: > > Am I reading this correctly that your proposal is to use the following > syntax? > > execute sql (p1 integer, p2 varchar(50)) > do >select * from t where t.id = :p1 and t.name = :p2 > > So, no explicit positional parameter markers

Re: [Firebird-devel] Current value for parallel workers

2022-08-16 Thread Dmitry Yemanov
16.08.2022 13:02, Jiří Činčura wrote: Session context variable seems to be a good fit. Monitoring table looks like overkill. I think DBA may want a monitoring table (MON$WORKERS?) that shows how many workers are currently active, what attachment are they bound to, and what task

Re: [Firebird-devel] Current value for parallel workers

2022-08-16 Thread Dimitry Sibiryakov
Jiří Činčura wrote 16.08.2022 12:02: Not yet. How would you like to see it ? Monitoring table, session context variable, database_info item ? All above ? ;) Session context variable seems to be a good fit. Monitoring table looks like overkill. And database_info is inconvenient for end

Re: [Firebird-devel] Current value for parallel workers

2022-08-16 Thread Jiří Činčura
>Not yet. How would you like to see it ? Monitoring table, session > context variable, > database_info item ? All above ? ;) Session context variable seems to be a good fit. Monitoring table looks like overkill. And database_info is inconvenient for end users. > Should user session be

Re: [Firebird-devel] Current value for parallel workers

2022-08-16 Thread Vlad Khorsun
16.08.2022 12:26, Jiří Činčura wrote: Hi *, Is there a way to get current value of parallel workers (from i.e. monitoring tables)? Not yet. How would you like to see it ? Monitoring table, session context variable, database_info item ? All above ? ;) Should user session be allowed to

[Firebird-devel] Current value for parallel workers

2022-08-16 Thread Jiří Činčura
Hi *, Is there a way to get current value of parallel workers (from i.e. monitoring tables)? -- 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] New statement: EXECUTE SQL

2022-08-16 Thread Jiří Činčura
>Can we just have named parameters support in Firebird before this feature > so > client parser will be not needed at all?.. That would be great. :) -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at

Re: [Firebird-devel] New statement: EXECUTE SQL

2022-08-16 Thread Dimitry Sibiryakov
Adriano dos Santos Fernandes wrote 16.08.2022 3:25: No, I expect that client parsers may not do unnecessary things, at least with this statement. Can we just have named parameters support in Firebird before this feature so client parser will be not needed at all?.. -- WBR, SD.

Re: [Firebird-devel] op_que_events and database shutdown

2022-08-16 Thread Jiří Činčura
> Are aux connections closed when a database is shutdown? In that case you > should be able to detect the connection close. As I wrote in my initially, the socket is not closed. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at

Re: [Firebird-devel] op_que_events and database shutdown

2022-08-16 Thread Mark Rotteveel
On 16-08-2022 11:01, Vlad Khorsun wrote: 16.08.2022 11:26, Jiří Činčura wrote: I just want to know there's nothing on protocol level I can use to help this situation. No response. So I suppose nothing?   I didn't found anything suitable. Are aux connections closed when a database is

Re: [Firebird-devel] op_que_events and database shutdown

2022-08-16 Thread Vlad Khorsun
16.08.2022 11:26, Jiří Činčura wrote: I just want to know there's nothing on protocol level I can use to help this situation. No response. So I suppose nothing? I didn't found anything suitable. Regards, Vlad Firebird-Devel mailing list, web interface at

Re: [Firebird-devel] op_que_events and database shutdown

2022-08-16 Thread Jiří Činčura
> I just want to know > there's nothing on protocol level I can use to help this situation. No response. So I suppose nothing? -- 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] New statement: EXECUTE SQL

2022-08-16 Thread Mark Rotteveel
On 15-08-2022 19:42, Vlad Khorsun wrote:   Also, I don't like 'sql' word, especially after 'execute statement' and 'execute block'. Too much, as for me :) Syntax with 'with' instead of 'execute sql' looks much better to me, but it is already used in CTE's, thus it seems as not the best

Re: [Firebird-devel] New statement: EXECUTE SQL

2022-08-16 Thread Mark Rotteveel
On 16-08-2022 03:25, Adriano dos Santos Fernandes wrote: On 15/08/2022 14:42, Vlad Khorsun wrote:   I like the idea but not syntax. As already mentioned, there it will be hard for app\component devs to parse the whole statement looking for parameters. Note, semicolon usually mark "client"