Im not sure what history of this fdb was, but I worked with it with Beta 1,
then long time with Beta 2...
Am Di., 13. Okt. 2020 um 16:19 Uhr schrieb Dimitry Sibiryakov <
s...@ibphoenix.com>:
> 13.10.2020 15:10, Pro Turm wrote:
> > Could anybody explain the reason for the error above ?
>
>This
Error message "expected length N, actual M" contains wrong value of M when
charset UTF8 is used in the field declaration of a table
---
Key: CORE-6414
"-607: unsuccessful metadata update "create table rep$xxxsth failed"
Could anybody explain the reason for the error above ?
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Error message "malformed string' is issued instead of "expected: N, actual : M"
when UTF-8 charset is used and default value for declared column is greater
than this column length
-
13.10.2020 15:10, Pro Turm wrote:
Could anybody explain the reason for the error above ?
This database was created with previous beta version. In unstable branch such things
happen.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/
Database: problem.fdb
internal Firebird consistency check (missing pointer page in DPM_data_pages
(243), file: dpm.cpp line: 779)
Could anybody explain the reason for the error above ?
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
I see value on it, but the task seems not easy.
First, let me say about problem in current parser (not only the parser):
It does not recover from errors and continue parsing (and doing
semantics analysis) to show all errors. It stops on first error.
This is very bad. I'm not saying it is impossi
On 2020-10-13 06:15, Arily Essen via Firebird-devel wrote:
2. (drawing on long-term experience)
- I have seen some old threads (for instance "BTYACC" starting on Dec
4, 2004) where pros/cons of different types of parsers and parser
generators were discussed in the context of porting/migration
13.10.2020 05:15, Arily Essen via Firebird-devel wrote:
- Are you satisfied with the current situation of the DSQL parser and its generator? Are
there particularly sore points in its maintenance? Perhaps you have a longstanding mental
list of how things could be improved there?
I'm not in co
