Em qui, 2 de set de 2021 16:31, Dimitry Sibiryakov
escreveu:
> Adriano dos Santos Fernandes wrote 02.09.2021 21:28:
> > The preprocessor could be used to generate that as well.
>
>Another custom preprocessor in addition to CLOOP?
>
C/C++ preprocessor.
Adriano
Firebird-Devel mailing list,
Adriano dos Santos Fernandes wrote 02.09.2021 21:28:
The preprocessor could be used to generate that as well.
Another custom preprocessor in addition to CLOOP?
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Em qui, 2 de set de 2021 15:23, Mark Rotteveel
escreveu:
>
> The nice thing about the current solution is that it produces a database
> that is queryable, and I use that to generate the message and sqlstate
> files of Jaybird, and the list of error messages and codes in the
> language reference.
On 2021-09-02 17:46, Adriano dos Santos Fernandes wrote:
We have still traces of the old error message processing that only
complicate things.
We define errors in .sql files (it was database) and then everything is
as before.
We have generated files in the tree, which frequently causes merge
Adriano dos Santos Fernandes wrote 02.09.2021 18:21:
Do you suggest to get rid of firebird.msg (including localized
versions) altogether?
No. Utility that today reads a database will be compiled including the
header file and will generate firebird.msg as today.
That's pity. It is a dead
On 02/09/2021 13:12, Dimitry Sibiryakov wrote:
> Adriano dos Santos Fernandes wrote 02.09.2021 17:46:
>> That makes no sense IMHO and I propose a change to make things simpler
>> and faster.
>>
>> We define error messages (and all necessary things) in .h files and with
>> help of the preprocessor
Adriano dos Santos Fernandes wrote 02.09.2021 17:46:
That makes no sense IMHO and I propose a change to make things simpler
and faster.
We define error messages (and all necessary things) in .h files and with
help of the preprocessor (from the compiler) we use them (something like
done in
Hi!
We have still traces of the old error message processing that only
complicate things.
We define errors in .sql files (it was database) and then everything is
as before.
We have generated files in the tree, which frequently causes merge
conflicts, not very simple to fix, as generated files
On 02-09-2021 10:08, Omacht András wrote:
Summary: for our point of view mysql and oracle is the easiest to use as a
programmer (and maybe a data analyst who has the right to write queries).
Postre, mssql bring the solution what at least we expected and what Attila
outlined.
Firebird is
31.08.2021 23:53, Mark Rotteveel wrote:
The only debatable feature of dialect 3 division is the fact the
calculation stops (equivalent to floor rounding), while reduction of
scale through assignment or cast applies half-up rounding
"Whether to round or truncate when performing division is
We made a quick review with http://sqlfiddle.com
Numeric test:
create table teszt01(n1 numeric(15,2), n2 numeric(15,2), n3 numeric(15,2));
insert into teszt01(n1, n2) values (1, 3);
insert into teszt01(n1, n2) values (2, 3);
update teszt01 set n3 = n1 / n2 * 100;
select * from teszt01;
Integer
11 matches
Mail list logo
