put parameters in positional syntax. And EXECUTE PROCEDURE is easy to
return all output parameters, but its syntax is awful in others ways
(many variants, too much verbose).
Adriano
On 31/05/2021 10:19, Adriano dos Santos Fernandes wrote:
> Hi!
>
> EXECUTE PROCEDURE is full of weir
On 15/09/2022 08:18, Alex Peshkoff via Firebird-devel wrote:
> On 9/15/22 14:00, Adriano dos Santos Fernandes wrote:
>> Em qui., 15 de set. de 2022 07:06, Alex Peshkoff via Firebird-devel
>> escreveu:
>>
>> >
>> > Why don't force build with stat
On 15/09/2022 07:52, Mark Rotteveel wrote:
> On 15-09-2022 03:52, Adriano dos Santos Fernandes wrote:
>> On 05/09/2022 08:13, Mark Rotteveel wrote:
>>> That is not really embedded IMHO. Firebird Embedded with Firebird 3.0
>>> has become unwieldy and even harder t
Em qui., 15 de set. de 2022 07:06, Alex Peshkoff via Firebird-devel <
firebird-devel@lists.sourceforge.net> escreveu:
> >
> > Why don't force build with static libs?
> >
>
> In what way it's better than own dynamic libraries?
>
Not put files in system lib outside of a package manager.
On 05/09/2022 08:13, Mark Rotteveel wrote:
> On 05-09-2022 13:00, Alex Peshkoff via Firebird-devel wrote:
>> When adding it I cared about an ability to fix secirtiy issues in
>> 3d-party libraries not rebuilding and reinstalling FB packages. With
>> used schema one can simply install fixed system
On 05/09/2022 07:20, Mark Rotteveel wrote:
>
> That is part of the figuring out. I don't normally write shell scripts
> either, but before that I would also need to figure out exactly what I
> need to do before I can even start on that.
>
> And since I consider this packaging Firebird embedded
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
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
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-withDebugSy
On 24/08/2022 09:32, Alex Peshkoff via Firebird-devel wrote:
> On 8/24/22 15:03, Adriano dos Santos Fernandes wrote:
>> On 24/08/2022 08:59, Mark Rotteveel wrote:
>>> On 24-08-2022 13:45, Adriano dos Santos Fernandes wrote:
>>>> This is our Firebird 4.0.2 released
On 24/08/2022 12:04, Alex Peshkoff via Firebird-devel wrote:
>>
>> The Linux builds are not complete builds compared to Windows pdb
>> builds (e.g. config files, documentation, security database, etc are
>> missing)
>>
>
> Yep, they contain only binaries with debug-info.
>
Linux "debuginfo"
On 24/08/2022 12:33, Paul Reeves wrote:
> On Wed, 24 Aug 2022 16:04:20 +0200
> Mark Rotteveel wrote:
>
>> On 24-08-2022 15:36, Dimitry Sibiryakov wrote:
>>> Mark Rotteveel wrote 24.08.2022 15:32:
If the term is confusing or ambiguous, it already is so in its current
form.
>>>
>>>
On 24/08/2022 08:59, Mark Rotteveel wrote:
> On 24-08-2022 13:45, Adriano dos Santos Fernandes wrote:
>> This is our Firebird 4.0.2 released files:
>>
> [..]
>> It's difficult to understand, they do not mention OS and hardware
>> architectures are inconsistent.
>&g
Hi!
This is our Firebird 4.0.2 released files:
Firebird-4.0.2.2816-0-Win32-pdb.exe
Firebird-4.0.2.2816-0-Win32-pdb.zip
Firebird-4.0.2.2816-0-Win32.exe
Firebird-4.0.2.2816-0-Win32.zip
Firebird-4.0.2.2816-0-x64-pdb.exe
Firebird-4.0.2.2816-0-x64-pdb.zip
Firebird-4.0.2.2816-0-x64.exe
On 23/08/2022 07:53, Simonov Denis via Firebird-devel wrote:
> 23.08.2022 13:38, Norbert Saint Georges пишет:
>> Simonov Denis via Firebird-devel a écrit :
>>> SQL> connect inet://localhost:3055/employee user SYSDBA password
>>> 'masterkey';
>>> Database: inet://localhost:3055/employee, User:
On 22/08/2022 08:24, Gabor Boros wrote:
> Hi All,
>
> Isn't that too much?
> In Gabor's ideal world..., GitHub CI "from a branch"=snapshot, "from a
> tag"=release. :-)
>
> It's just a technical question from me, not more not less.
> For example if release and snapshot use the same build
On 19/08/2022 05:09, Mark Rotteveel wrote:
> On 19-08-2022 02:36, Adriano dos Santos Fernandes wrote:
>> On 18/08/2022 04:37, Mark Rotteveel wrote:
>>> In other words, most specific type with the highest
>>> precision/scale/length. When confronted with combinati
On 19/08/2022 06:06, Tony Whyman wrote:
> On 19/08/2022 00:42, Adriano dos Santos Fernandes wrote:
>> On 18/08/2022 18:53, Tony Whyman wrote:
>>> IBX for Lazaus follows the original Deplhi IBX approach of adopting PSQL
>>> syntax for named parameters.
>>
On 18/08/2022 04:37, Mark Rotteveel wrote:
> My guess is that they either:
>
> 1) don't allow mixing types
> 2) use the most specific type that is compatible with all positions,
> otherwise error
> 3) use the first position
> 4) use the last position
>
> I think rule 2 is probably the best, but
On 18/08/2022 04:01, Mark Rotteveel wrote:
> On 18-08-2022 04:02, Adriano dos Santos Fernandes wrote:
>> How are client libraries (Jaybird, .NET Provider, Delphi ones)
>> describing its named parameters to their users?
>>
>> I mean, given this SQL:
>>
&g
On 18/08/2022 04:42, Jiří Činčura wrote:
> In .NET parameters are named `@param`, aka the delimiter is `@`.
>
>> I suppose you transform this to:
>>
>> select *
>> from rdb$database
>> where ? = 1 or ? = '2'
>
> Correct.
>
>> Which will map to two Firebird parameters with different types.
>
On 18/08/2022 18:53, Tony Whyman wrote:
> IBX for Lazaus follows the original Deplhi IBX approach of adopting PSQL
> syntax for named parameters.
Can a name be used more than once, and if yes, how is its type deduction?
Adriano
Firebird-Devel mailing list, web interface at
Hi Mark, Jiri, all!
How are client libraries (Jaybird, .NET Provider, Delphi ones)
describing its named parameters to their users?
I mean, given this SQL:
select *
from rdb$database
where :param = 1 or :param = '2'
We have here single name used in context with multiple types.
I suppose
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
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" named parameters and it will be near to
> impossible
On 15/08/2022 16:20, Dimitry Sibiryakov wrote:
> I see no difference between proposed syntax and WITH except of
> definition of functions instead of derived tables in CTE part.
> What is wrong with expanding it into something like this:
>
> WITH
I prefer to not reuse a standard keyword for
On 15/08/2022 14:47, Dmitry Yemanov wrote:
> using (p1 integer = :p1, p2 varchar(255) = :p2)
> do select * from t where t.id = :p1 and t.name = :p2
I like this one.
Or replacing USING by GIVEN.
I'm not sure the parameter-less case is nice:
using
declare function ...
do
...
Adriano
On 15/08/2022 07:27, Dimitry Sibiryakov wrote:
> Adriano dos Santos Fernandes wrote 15.08.2022 12:24:
>> Firebird does not have any support for client named parameters.
>
> IMessageMetadata has field for name which is currently unused. What
> else client support d
On 15/08/2022 04:16, Simonov Denis via Firebird-devel wrote:
>
> Very good feature, reminds me of the functionality from Oracle
>
> WITH Procedure p1 ...
> AS
> ...
> FUNCTION f1 ...
> AS
> ...
> SELECT...
>
Plus, DECLARE VAR := ?
But things are very less useful for them due to their
Em dom., 14 de ago. de 2022 03:55, Mark Rotteveel
escreveu:
>
>
> Would this still allow the full SELECT syntax (including WITH clauses,
> OFFSET/FETCH, GROUP BY, etc), and things like RETURNING for INSERT, etc?
>
Yes.
> I assume this is a toplevel statement only, so it can't occur as a
>
On 13/08/2022 20:28, Adriano dos Santos Fernandes wrote:
> and it's to use with SELECT, UPDATE, DELETE and MERGE
And also INSERT and UPDATE OR INSERT...
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Hi!
When one starts with a DSQL command and need to adapt it to EXECUTE BLOCK
(for example to use sub routines or use a single parameter in many places),
work is difficult when there are many parameters and output fields.
Everything must be explicitly declared.
I propose new DSQL statement that
Em 11/08/2022 12:58, Vlad Khorsun escreveu:
11.08.2022 17:26, Mark Rotteveel wrote:
On 11-08-2022 16:21, Vlad Khorsun wrote:
11.08.2022 17:10, Mark Rotteveel wrote:
Why was this NULL behaviour chosen?
To make BLOB_APPEND more convenient for users.
I don't understand how using a
Em 05/08/2022 06:40, Jiří Činčura escreveu:
Hi *,
What's the DPB tag for collation when creating database. For charset there's
isc_dpb_set_db_charset.
There isn't one.
CREATE DATABASE immediately executes a ALTER CHARACTER SET SET
DEFAULT COLLATION.
Adriano
Firebird-Devel mailing
Em 07/07/2022 11:12, Gabor Boros escreveu:
Hi All,
4.0.2 not released or tagged yet. Why some issues have these labels?
https://github.com/FirebirdSQL/firebird/issues?q=label%3A%22affect-version%3A+4.0.2%22+
On 26/06/2022 03:55, Vlad Khorsun wrote:
> 26.06.2022 2:32, Adriano dos Santos Fernandes wrote:
>> Em sáb., 25 de jun. de 2022 20:15, Vlad Khorsun escreveu:
>>
>> 26.06.2022 1:31, Adriano dos Santos Fernandes wrote:
>> > Em sáb., 25 de jun. de 202
Em sáb., 25 de jun. de 2022 20:15, Vlad Khorsun
escreveu:
> 26.06.2022 1:31, Adriano dos Santos Fernandes wrote:
> > Em sáb., 25 de jun. de 2022 18:46, Vlad Khorsun escreveu:
>
>
>I see, thanks. Actually, restore is OK, the problem is that it reported
> reason
> wh
Em sáb., 25 de jun. de 2022 18:46, Vlad Khorsun
escreveu:
> 25.06.2022 23:59, Adriano dos Santos Fernandes wrote:
> > Hi!
> >
> > After these changes, restore of dialect 1 databases with keywords are
> > making TCS tests fail with this content (or example):
> >
On 22/06/2022 11:01, Ilya Eremin wrote:
> Hello!
>
> In FB3+, when I create an index on a table's field and then drop this
> table, DROP INDEX DDL triggers are not called. Is it done this way on
> purpose? I did not find a clear description of such case in the
> documentation.
>
This is as
Hi!
After these changes, restore of dialect 1 databases with keywords are
making TCS tests fail with this content (or example):
gbak: ERROR:Dynamic SQL Error
gbak: ERROR:SQL error code = -104
gbak: ERROR:Token unknown - line 1, column 47
gbak: ERROR:POSITION
Adriano
Em sex., 17 de jun. de 2022 07:27, Paul Reeves
escreveu:
>
> We are currently doing this sort if thing in several batch files:
>
> if defined VS170COMNTOOLS () else
> if defined VS160COMNTOOLS () else
> if defined VS150COMNTOOLS () else
>
> which is very messy and hard to maintain.
>
> I've been
On Thu, Jun 16, 2022 at 1:38 AM Dmitry Yemanov wrote:
>
> See:
>
>
> https://github.com/FirebirdSQL/firebird/commit/c8c7c3a44dad9572a55d6fed68f1c399a19366db
>
> Initially (FB2) the code was:
>
> if (GetFileType(in) == FILE_TYPE_DISK)
>Interactive = false;
>
> then (circa 2.5) it was changed
On Wed, Jun 15, 2022 at 6:31 PM Dimitry Sibiryakov wrote:
> Adriano dos Santos Fernandes wrote 15.06.2022 21:56:
> > Are there any reason for that?
>
>MSYS (and I suspect WSL as well) bash is using unnamed pipes to
> redirect
> input and output of applications int
Hi!
In Linux, when we do:
echo "select 1 from rdb\$database; select 2 from rdb\$database;" | isql
t.fdb
It shows:
CONSTANT
1
CONSTANT
2
In Windows,
echo select 1 from rdb$database; select 2 from rdb$database; | isql t.fdb
It shows:
On 09/06/2022 09:58, Dmitry Yemanov wrote:
> 09.06.2022 15:16, Adriano dos Santos Fernandes wrote:
>
> Yes, it should work. However, I'm not going to remove the limit until we
> introduce a denser compression. Also, we have a number of places where
> records is stored unpacked i
On 09/06/2022 09:29, Dimitry Sibiryakov wrote:
> Adriano dos Santos Fernandes wrote 09.06.2022 14:16:
>> What do you think and are there any active work in this regard?
>
> Using of record encoding instead of record compressing was suggested
> years ago by Ann and Jim.
Ye
Hi!
With some frequency people ask me why UTF-8 is slower than single byte
charsets.
The thing is, they have something using, for example, VARCHAR(30)
CHARACTER SET WIN1252 and convert to VARCHAR(30) CHARACTER SET UTF8,
test with the same data and have slower queries.
Database is also increased
On 02/06/2022 08:08, Dimitry Sibiryakov wrote:
> Alex Peshkoff via Firebird-devel wrote 02.06.2022 13:01:
>>> It is "ALTER TABLE" which must be executed on replica. Otherwise
>>> you'll have problem with ALTER TABLE ADD FIELD.
>>
>> Is it impossible to analyze clauses of statement?
>
>
Hi!
Isn't this thread unsafe?
struct event_t
{
SLONG event_count;
int pid;
pthread_mutex_t event_mutex[1];
pthread_cond_t event_cond[1];
};
int SharedMemoryBase::eventPost(event_t* event)
{
...
++event->event_count;
...
}
Should not
On 17/05/2022 09:54, Mark Rotteveel wrote:
>
> Thanks! I will change Jaybird to switch to using blr_varying2/blr_text2
> for Jaybird 4.0.7 and Jaybird 5.
>
When you did it for test, did you used the charset number or CS_dynamic?
I'm asking because the current code seems to have the same
On 17/05/2022 08:30, Mark Rotteveel wrote:
>> Is this happening with fbclient library too?
>
> Good question: no it doesn't. Which suggests Jaybird is doing something
> different. Jaybird uses blr_varying/blr_text, not blr_varying2/blr_text2
> when sending the BLR of the execute. Could that make
On 16/05/2022 12:07, Mark Rotteveel wrote:
> On 16-05-2022 16:50, Mark Rotteveel wrote:
>> I was running some tests against Firebird-5.0.0.494-0_x64 (latest
>> snapshot, from last Saturday), and I notice that I get incorrect
>> string right truncation errors with CHAR/VARCHAR.
>>
>> I currently
On 11/05/2022 16:03, Roman Simakov wrote:
>
> SQL SECURITY replaces an effective user for some time. Can you use the
> same trick while profiler initializing?
>
No.
Profiler plugin creates tables and views and grant access to them to
role PLG$PROFILER that is grated to users.
Users directly
On 11/05/2022 14:47, Roman Simakov wrote:
>
> I was thinking the profiler should not touch profiled attachments at
> all. It might influence its logic.
>
The profiler should work on its initial usage when it creates its metadata.
This is priority for me than theoretical problems due to roles
On 11/05/2022 11:55, Roman Simakov wrote:
> Can you make up or describe a potential case of the situation?
> Undoubtedly the feature would be useful but we've lived without it for
> all the time.
>
In the profiler, I will create a role, the tables and views in another
connection. I'll grant
Hi!
When roles are default granted to an user, they are not immediately
reflected in the attachments.
Attachments need to issue a SET ROLE which should be different than
currently used, then another SET ROLE to the correct one to refresh the
roles. Or re-attach.
I think we should improve that
On 10/05/2022 05:21, Roman Simakov wrote:
> It makes sense. Could you create a ticket?
>
https://github.com/FirebirdSQL/firebird/issues/7178
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Hi!
A role can be default granted to PUBLIC.
create role r1;
grant default r1 to public;
In this case I think the role should be act as a defaulted role to every
user.
But it's not working.
The role privileges only works if user uses it explicitly.
Adriano
Firebird-Devel mailing list, web
On 28/04/2022 05:37, Mark Rotteveel wrote:
> Our travis-ci builds haven't actually run for the past 10 months as we
> ran out of credits. As no one has noticed this in that time, it looks
> like the travis-ci builds serve no actual purpose.
>
> Any objections if I remove the travis-ci build
On 13/04/2022 12:24, Alex Peshkoff via Firebird-devel wrote:
> We have one test failing on linux - bugs/core_1885.fbt. Create collation
> should fail with some option, but it succeeds. uppose due to upgrade of
> ICU on linux test server.
> In other aspects I suppose we are ready for release.
>
I
On 16/03/2022 00:45, Dmitry Yemanov wrote:
> 15.03.2022 21:43, Adriano dos Santos Fernandes wrote:
>>
>>> In fact, what you priorly define as LT is IMO "declared" LTT.
>>
>> I had that impression before read the standard, but then I changed my
>> op
On 15/03/2022 15:20, Vlad Khorsun wrote:
>> So CREATEd LTTs cannot be used in PSQL routines, only by DSQL?
>
> At first look I see two way's to go:
> a) PSQL routines can't see CREATE'd LTT's, or
> b) PSQL routines can see and use LTT definition that exists at the
> moment of routine
>
On 15/03/2022 15:00, Adriano dos Santos Fernandes wrote:
>> Would it be possible to use some other word to distinguish, instead of
>> just leaving out "local" (which essentially loses the most important
>> aspect of what it really is)?
>>
>> Suggestions
On 15/03/2022 14:07, Dmitry Yemanov wrote:
> 15.03.2022 17:14, Adriano dos Santos Fernandes wrote:
>>
>> As part of "Support multiple rows for DML RETURNING (#6815)" feature,
>> BLR verbs for "local table" were created.
>>
>> Local tables (L
On 15/03/2022 13:00, Dimitry Sibiryakov wrote:
> Adriano dos Santos Fernandes wrote 15.03.2022 15:37:
>> On 15/03/2022 11:23, Alex Peshkoff via Firebird-devel wrote:
>>> Very interesting - but other name for them should be used. It's too easy
>>> to loose
On 15/03/2022 14:02, Vlad Khorsun wrote:
>
>> SQL standard defines LOCAL TEMPORARY TABLES (LTT), which may be
>> "created" or "declared". The semantics of these standard specs are
>> different and not very easy applicable to Firebird as they are based on
>> standard notion of modules, that is not
On 15/03/2022 12:03, Kjell Rilbe wrote:
> Den 2022-03-15 kl. 15:37, skrev Adriano dos Santos Fernandes:
>> On 15/03/2022 11:23, Alex Peshkoff via Firebird-devel wrote:
>>> Very interesting - but other name for them should be used. It's too easy
>>> to loose
On 15/03/2022 14:39, Vlad Khorsun wrote:
> 15.03.2022 19:27, Dmitry Yemanov wrote:
>> 15.03.2022 20:17, Vlad Khorsun wrote:
>>>
For me, "created" LTT is similar to GTT (i.e. stored in the schema)
but with data isolated per request (per PSQL routine).
>>>
>>> I'd consider about CREATE'd
On 15/03/2022 11:23, Alex Peshkoff via Firebird-devel wrote:
>
> Very interesting - but other name for them should be used. It's too easy
> to loose difference between LT & LTT that are absolutely different things.
>
Maybe just "DECLARE TABLE" then?
We would refer to them as "declared tables".
Hi!
As part of "Support multiple rows for DML RETURNING (#6815)" feature,
BLR verbs for "local table" were created.
Local tables (LT) as defined there works outside transaction control.
For #6815 this does not matter, but I want to add LT feature that will
use these verbs.
LTs are defined
On 03/03/2022 14:19, Alex Peshkoff via Firebird-devel wrote:
> On 2/28/22 20:30, Adriano dos Santos Fernandes wrote:
>> On 28/02/2022 13:18, Alex Peshkoff via Firebird-devel wrote:
>>> I suppose it's with mentoned 2Mb cache.
>> Yes. But it's the same even with 100K a
On 3/2/22 05:17, Jiří Činčura wrote:
>> But before attachment is done that does not happen and strings are
>> returned as is (for example, error about non-existent file in Windows
>> ANSI encoding).
>>
>> To convert charsets, database must be opened currently.
>
> That's sad. I'm facing exactly
Hi!
Do we have any good reason to make this method do for internal requests
everything it does for user's statement?
Or could we start it with this?
void Statement::verifyAccess(thread_db* tdbb)
{
if (flags & FLAG_INTERNAL)
return;
...
}
Adriano
On 01/03/2022 13:19, Karol Bieniaszewski wrote:
> Hi
>
>
>
> Snapshots are not avilable
>
You may download non-official snapshot builds here (logged with github):
https://github.com/FirebirdSQL/firebird/actions
Adriano
Firebird-Devel mailing list, web interface at
On 28/02/2022 13:18, Alex Peshkoff via Firebird-devel wrote:
> I suppose it's with mentoned 2Mb cache.
Yes. But it's the same even with 100K as the test uses very few and
small statements.
>
> One more question. Suppose some statement remains in a cache for very
> long time cause it's reused
On 26/02/2022 22:05, Adriano dos Santos Fernandes wrote:
>
> I will report back some numbers (memory, prepare times).
>
Here is a performance test I did: https://pastebin.com/3UnB5BNU
It's relative simple (not much indices) and common metadata.
It's tested as whole (create databas
On 28/02/2022 07:17, Alex Peshkoff via Firebird-devel wrote:
> On 2/28/22 13:10, Jiří Činčura wrote:
>> Hi *,
>>
>> If I get pointer to a string in isc_arg_string in status vector the
>> encoding is UTF8 if isc_dpb_utf8_filename was specified and
>> ANSI/system charset when isc_dpb_utf8_filename
On 26/02/2022 14:43, Dmitry Yemanov wrote:
> 26.02.2022 17:14, Adriano dos Santos Fernandes wrote:
>>
>> I do want to define default cache size.
>>
>> I'm thinking in 2M.
>>
>> Comments?
>
> We need to start with something, so why not. However, it wo
Hi!
I do want to define default cache size.
I'm thinking in 2M.
Comments?
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 23/02/2022 06:40, Jiří Činčura wrote:
>> You mean, running in the browser?
>
> Yes. Or any other place where WASM is/will be supported.
>
I had a (very) brief look at it once.
Main difficulties should be:
- Memory manager - no mmap
- Shared libraries
- File I/O
- Lock manager
All these
Em qua., 23 de fev. de 2022 04:51, Jiří Činčura escreveu:
> Hi *,
>
> Was there ever a discussion about providing Firebird build for WASM? I
> mean, having Firebird Embedded in WASM would be sick.
>
You mean, running in the browser?
Adriano
Firebird-Devel mailing list, web interface at
On 15/02/2022 08:28, Dmitry Yemanov wrote:
>
> Any other comments?
>
Would not it be possible to use some form of varint encoding (VLQ) there?
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 14/02/2022 10:43, Alex Peshkoff via Firebird-devel wrote:
>
> - AST (yes, 'A'-async is wrong tday, but I use traditional term) processing
That is the part I was missing, thanks.
BTW in thread_db::reschedule() we have:
-
void thread_db::reschedule()
{
// Somebody has kindly
Hi!
What is the importance of JRD_reschedule today?
More specifically speaking, verifying contention and "checking out"?
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 10/02/2022 14:44, Dmitry Yemanov wrote:
> 10.02.2022 20:18, Adriano dos Santos Fernandes wrote:
>>
>> We should have better strategy for request cache inside the statement.
>> If they are cheap to create, it would make no sense to never destroy
>> them like now
On 10/02/2022 12:30, Vlad Khorsun wrote:
> So, main benefit visible to end-user is to save prepare and check access
> time, correct ?
Yes.
> Also, good written apps (that re-uses prepared statements)
> will not see much changes - at least until impl of shared metadata cache.
>
I consider
On 10/02/2022 14:13, Dimitry Sibiryakov wrote:
> Dmitry Yemanov wrote 10.02.2022 18:07:
>>> But as I said and Vlad also said, we can remove roles from key and
>>> verify (with verification cache) after get statement from cache. This
>>> would be better.
>>
>> Yes, this gets my vote too.
>
> On
On 10/02/2022 13:13, Dmitry Yemanov wrote:
> 08.02.2022 16:36, Adriano dos Santos Fernandes wrote:
>>
>> First what should be the statement key in the cache?
>>
>> I've peek these:
>> - statement text
>> - clientDialect
>> - isInternalRequest
>>
On 10/02/2022 13:34, Dimitry Sibiryakov wrote:
> Dmitry Yemanov wrote 10.02.2022 17:28:
>>> Only if such translation is made right. Remember charset introducers.
>>
>> They're a problem, but it may only cause a cache miss, not a false
>> match, right?
>
> Yes, they can only cause miss but I'm
On 10/02/2022 13:28, Dmitry Yemanov wrote:
>
> In the ideal world, maybe. But this is *much* more complicated than it
> seems at the first glance.
>
I'd even go further and say we should not slow down things to catch this.
Adriano
Firebird-Devel mailing list, web interface at
On 10/02/2022 13:21, Dimitry Sibiryakov wrote:
> Dmitry Yemanov wrote 10.02.2022 17:13:
>> Cannot the UTF8-translated SQL text (which is currently inside
>> Statement::sqlText) be the key, to avoid dependency on the charset? I
>> don't think that semantically different statements may have the same
On 10/02/2022 13:20, Dmitry Yemanov wrote:
> 10.02.2022 16:01, Adriano dos Santos Fernandes wrote:
>>
>> (Jrd)Statement is reused - new jrd_req are get from same statement.
>
> IIRC, the existing cache of internal requests preserves jrd_req's. Am I
> right that afte
On 10/02/2022 13:20, Dmitry Yemanov wrote:
> 10.02.2022 16:01, Adriano dos Santos Fernandes wrote:
>>
>> (Jrd)Statement is reused - new jrd_req are get from same statement.
>
> IIRC, the existing cache of internal requests preserves jrd_req's. Am I
> right that afte
On 10/02/2022 12:43, Dmitry Yemanov wrote:
> 10.02.2022 15:57, Adriano dos Santos Fernandes wrote:
>>
>>>
>>> If we need to take roles into an account - only for attachment with same
>>> USER.
>>
>> Even without shared cache, user can change its rol
On 10/02/2022 10:04, Dimitry Sibiryakov wrote:
> Adriano dos Santos Fernandes wrote 10.02.2022 13:56:
>> But it's not surprise that many applications are not well coded and
>> sometimes does not do this. Competitor DBMSs has cache and works well in
>> this case too.
>
&g
On 10/02/2022 07:36, Dimitry Sibiryakov wrote:
> Alex Peshkoff via Firebird-devel wrote 10.02.2022 10:59:
>>> If\when shared metadata will be implemented - will it be possible to
>>> use cached compiled statement created in one attachment to use by
>>> another
>>> attachment ?
>>
>> If we need
On 10/02/2022 06:59, Alex Peshkoff via Firebird-devel wrote:
>
> If we need to take roles into an account - only for attachment with same
> USER.
>
Even without shared cache, user can change its roles with SET ROLES and
new prepared statements should work as before even when they were
On 10/02/2022 06:44, Vlad Khorsun wrote:
> 08.02.2022 15:36, Adriano dos Santos Fernandes wrote:
>> Hi!
>>
>> I have refactored DSQL statements/requests (continued worked of many
>> time ago) to separate shared (statement) and specific (request) parts.
>>
>>
Hi!
I have refactored DSQL statements/requests (continued worked of many
time ago) to separate shared (statement) and specific (request) parts.
It seems this ground work for compiled statement cache is complete and I
have even did a (very very) initial version of a compiled statement
cache
On 03/02/2022 12:39, Dimitry Sibiryakov wrote:
> Hello All.
>
> Remember me please why isc_lc_ctype isn't used to determine encoding
> of database name and DPB values?
> BTW, service name during service attach isn't converted into UTF-8 at
> all.
>
Character set discovery from name
1 - 100 of 1691 matches
Mail list logo
