Re: [Firebird-devel] Protocol version 13 weird behavior
Please check these urls too. http://tracker.firebirdsql.org/browse/CORE-2897 https://github.com/asfernandes/firebird/commit/c41493c756cdd6c7118e396aeec814f1b14bed3a 2016-03-09 5:14 GMT+09:00 Jiří Činčura : > > Check org.firebirdsql.gds.ng.wire.v13.V13Statement in Jaybird, it > > handles the writing and reading of rows in the protocol v13. > > Thanks. > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > > -- > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://makebettercode.com/inteldaal-eval > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel > -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-evalFirebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Protocol version 13 weird behavior
> Check org.firebirdsql.gds.ng.wire.v13.V13Statement in Jaybird, it > handles the writing and reading of rows in the protocol v13. Thanks. -- Mgr. Jiří Činčura Independent IT Specialist -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Protocol version 13 weird behavior
On 2016-03-08 20:49, Jiří Činčura wrote: >> Did you implement the new null bitmask? > > Ahh, this might be the problem. Some link to tracker? Or description? Check org.firebirdsql.gds.ng.wire.v13.V13Statement in Jaybird, it handles the writing and reading of rows in the protocol v13. Mark -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] How to create an alternative security database during restore?
> In my scenario I don't have shell access to server, onyl remote > access via ssh. > I've a 2.5 gbak file and a 3.0 server running. > > I was trying to restore the database without sysdba account and with > only editing database.conf once. This is currently not possible. > > I'll investigate the situation a little bit further in the next > days... And what magic helps you to edit databases.conf without shell access to server? Something like NFS? Must say that any ability to initialize security database remotely looks at the first glance like security risk. I will try to find some way to solve that problem but do not promise to have a solution. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Protocol version 13 weird behavior
> Did you implement the new null bitmask? Ahh, this might be the problem. Some link to tracker? Or description? -- Mgr. Jiří Činčura Independent IT Specialist -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Protocol version 13 weird behavior
Did you implement the new null bitmask? Mark - Bericht beantwoorden - Van: "Jiří Činčura" Aan: "For discussion among Firebird Developers" Onderwerp: [Firebird-devel] Protocol version 13 weird behavior Datum: di, mrt. 8, 2016 20:32 Hi *, Interestingly when I turn on protocol version 13 (which is really just a 12 with Srp currently in provider), for some statements (insert KO, create table OK, for example) I'm getting no data in response buffer from server after op_execute. There's just 0 bytes waiting for me. Is there some change between these two? Probably it's some lingering stuff in my protocol implementation, but maybe I'm lucky with "just" change. I'm still looking where I might be loosing some bytes or whatnot. Some clues are welcome as well. -- Mgr. Jiří Činčura Independent IT Specialist -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-evalFirebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Protocol version 13 weird behavior
Hi *, Interestingly when I turn on protocol version 13 (which is really just a 12 with Srp currently in provider), for some statements (insert KO, create table OK, for example) I'm getting no data in response buffer from server after op_execute. There's just 0 bytes waiting for me. Is there some change between these two? Probably it's some lingering stuff in my protocol implementation, but maybe I'm lucky with "just" change. I'm still looking where I might be loosing some bytes or whatnot. Some clues are welcome as well. -- Mgr. Jiří Činčura Independent IT Specialist -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5141) Field definition allow several NOT NULL clauses
Field definition allow several NOT NULL clauses --- Key: CORE-5141 URL: http://tracker.firebirdsql.org/browse/CORE-5141 Project: Firebird Core Issue Type: Bug Components: Engine Affects Versions: 4.0 Initial, 3.0 RC2 Reporter: Dimitry Sibiryakov Priority: Trivial Query like this should produce error: create table t (a integer not null not null not null) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Bool predicate with IS and parameter
> NOT DISTINCT, don't you? I swear I tried that before I sent the question. And it didn't work. Now it works. Maybe I changed something in provider... Confused. -- Mgr. Jiří Činčura Independent IT Specialist -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 21:00, Dimitry Sibiryakov wrote: > > Should I put it into tracker to let the change be documented as an > incompatibility with > previous versions? Yes, please. Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 18:16, Dmitry Yemanov wrote: > Looks OK to me. Should I put it into tracker to let the change be documented as an incompatibility with previous versions? -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Bool predicate with IS and parameter
Em 08/03/2016 11:15, Jiří Činčura escreveu: > Hi *, > > is there a way to write a predicate with BOOLEAN column and IS (in FB3)? > Something like `bool_col IS CAST(? as BOOLEAN)`? > You could do with = or NOT DISTINCT, don't you? Adriano -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
Em 08/03/2016 09:33, Dmitry Yemanov escreveu: > 06.03.2016 16:55, Dimitry Sibiryakov wrote: > > >> I think we need DE to make decision. > > The only way > > CREATE OR ALTER SEQUENCE S; > > can be allowed is that is acts as RESTART WITH 0 INCREMENT BY 1 for > existing sequences. > I then see lots of upset users and tracker tickets with this. :) Adriano -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 20:10, Dimitry Sibiryakov wrote: >> Do you want to throw a syntax error from the parser or something more >> intelligent like "duplicate constraint definitions are not allowed" from >> DdlNodes? > > Standard syntax error from parser is the simplest solution: > >> SQL> create table t (a integer not null not null); >> Statement failed, SQLSTATE = 42000 >> SQL error code = -637 >> -duplicate specification of NOT NULL - not supported > >> What about (a int primary key primary key)? Is it also allowed or NOT >> NULL is the only problem? > > It already works this way: > >> SQL> create table t (a integer primary key primary key); >> Statement failed, SQLSTATE = 27000 >> unsuccessful metadata update >> -CREATE TABLE T failed >> -action cancelled by trigger (3) to preserve data integrity >> -Attempt to define a second PRIMARY KEY for the same table > >> SQL> create table t (a integer unique unique); >> Statement failed, SQLSTATE = 42000 >> unsuccessful metadata update >> -CREATE TABLE T failed >> -Same set of columns cannot be used in more than one PRIMARY KEY and/or >> UNIQUE constraint definition Looks OK to me. Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5140) Wrong error message when user tries to set number of page buffers into not supported value
Wrong error message when user tries to set number of page buffers into not supported value -- Key: CORE-5140 URL: http://tracker.firebirdsql.org/browse/CORE-5140 Project: Firebird Core Issue Type: Bug Components: Engine Affects Versions: 3.0 RC2 Reporter: Vlad Khorsun Priority: Minor >gfix -b 1 bad parameters on attach or create database -Attempt to set in database number of buffers which is out of acceptable range [:] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
08.03.2016 17:46, Mark Rotteveel wrote: > I disagree, the current syntax conforms to the standard. Unless standard require to throw an error on this syntax, we don't violate it but expand for users' convenience. But as you wish. -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 17:59, Dmitry Yemanov wrote: > Do you want to throw a syntax error from the parser or something more > intelligent like "duplicate constraint definitions are not allowed" from > DdlNodes? Standard syntax error from parser is the simplest solution: > SQL> create table t (a integer not null not null); > Statement failed, SQLSTATE = 42000 > SQL error code = -637 > -duplicate specification of NOT NULL - not supported > What about (a int primary key primary key)? Is it also allowed or NOT > NULL is the only problem? It already works this way: > SQL> create table t (a integer primary key primary key); > Statement failed, SQLSTATE = 27000 > unsuccessful metadata update > -CREATE TABLE T failed > -action cancelled by trigger (3) to preserve data integrity > -Attempt to define a second PRIMARY KEY for the same table > SQL> create table t (a integer unique unique); > Statement failed, SQLSTATE = 42000 > unsuccessful metadata update > -CREATE TABLE T failed > -Same set of columns cannot be used in more than one PRIMARY KEY and/or > UNIQUE constraint definition -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
On 08/03/16 17:00, Dmitry Yemanov wrote: > 08.03.2016 19:06, Dimitry Sibiryakov wrote: > >> 05.03.2016 22:28, Lester Caine wrote: >>> It would be nice if we did not have re-order scripts from other >>> databases so >>>NOT NULL DEFAULT '30' >>> has to be >>>DEFAULT '30' NOT NULL >>> in Firebird. >> >> If DY agree, I can commit this change. > > I don't think we need to tweak our parser to please non-standard > database implementations. I think something like this does not cause any problems, but can be flagged as our flexibility when working with material from other sources. If M$ start pushing MSSQL on Linux then making the alternate switch to Firebird as easy as possible makes sense to me. -- Lester Caine - G8HFL - Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
08.03.2016 19:06, Dimitry Sibiryakov wrote: > 05.03.2016 22:28, Lester Caine wrote: >> It would be nice if we did not have re-order scripts from other >> databases so >>NOT NULL DEFAULT '30' >> has to be >>DEFAULT '30' NOT NULL >> in Firebird. > > If DY agree, I can commit this change. I don't think we need to tweak our parser to please non-standard database implementations. Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 19:51, Dimitry Sibiryakov wrote: > 08.03.2016 17:46, Dmitry Yemanov wrote: >>> "create table t (a integer not null not null not null)" is a valid syntax >>> or a bug? >> I'd call it a bug. A very minor one for sure. > > Am I allowed to commit a fix? Do you want to throw a syntax error from the parser or something more intelligent like "duplicate constraint definitions are not allowed" from DdlNodes? What about (a int primary key primary key)? Is it also allowed or NOT NULL is the only problem? Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
08.03.2016 19:50, Dimitry Sibiryakov wrote: > But you are still sure that "CREATE OR ALTER" must alter attributes that are > not > explicitly mentioned in query?.. I believe that both CREATE and ALTER parts should deliver the same object state. I agree that changing non-referenced attributes looks weird and may confuse users. I don't insist this is absolutely correct. But the only alternative is to reject such syntax, as we do now. I don't see any other options, sorry. Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
08.03.2016 17:45, Dmitry Yemanov wrote: >> But in this case behavior will be inconsistent with plain ALTER TABLE that >> doesn't >> >change not mentioned attributes. > We don't have CREATE OR ALTER for tables, do we? I just mistyped "ALTER SEQUENCE", sorry. >> >I hope you won't insist that "ALTER SEQUENCE s1 INCREMENT 3" must reset >> >value to 0?.. > Surely not. I was speaking about CREATE OR ALTER only. But you are still sure that "CREATE OR ALTER" must alter attributes that are not explicitly mentioned in query?.. -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 17:46, Dmitry Yemanov wrote: >> "create table t (a integer not null not null not null)" is a valid syntax or >> a bug? > I'd call it a bug. A very minor one for sure. Am I allowed to commit a fix? -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] BLR contexts limit
I"d use it as an excuse to dump BLR, or at least freeze and deprecate it. It serves no useful purpose and as you note, is an impediment to progress. It deserves to join slide rules, Beta Max, and four function calculators as footnotes in history books. On 3/8/2016 8:02 AM, Dmitry Yemanov wrote: > All, > > The good thing is that the code internals are more or less ready to work > with context/stream number of any size, thanks to Claudio's refactoring. > So the issue is mostly about BLR. > > I see two possible solutions: > > 1) Bump BLR version, make all context-aware verbs to generate/parse > longer numbers (prefixed by counter, variable-length encoded, whatever) > if new BLR version is used. Support old BLR versions, for sure (for > migration, message descriptions, etc) but generate new BLR version for > new objects. > > The major problem here is backward compatibility. BLR version 6 cannot > be parsed by prior engines, so backward migration via gbak becomes > impossible (at least after some metadata have been modified in FB4). > > Perhaps we could hack gbak to change the first byte of the every BLR > stream (fix the BLR version to the older one) during restore, but the > context encoding is incompatible anyway. > > Maybe we could teach the engine to recreate BLR based on the existing > source code during restore, but (1) it gonna work only if restoring with > v4 gbak, (2) source code may be missing, (3) I don't really like how it > would affect the layering, (4) it gonna be slower. > > 2) Another solution is to keep BLR version 5 but introduce new versions > of existing context-aware verbs. They will be used only for context > numbers > 255. > > Very dumb, but simplifies backward migration. Only databases with high > context numbers (read: with metadata objects re-implemented under FB4) > will be impossible to migrate. > > I'm not sure whether we have enough BLR code space for that though. > > Can anyone think of any better idea? I have the former solution > implemented, but maybe we could do something more clever? > > > Dmitry > > -- > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://makebettercode.com/inteldaal-eval > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Several NOT NULL constraints for the same field
08.03.2016 17:24, Dimitry Sibiryakov wrote: > > "create table t (a integer not null not null not null)" is a valid syntax or > a bug? I'd call it a bug. A very minor one for sure. Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
I disagree, the current syntax conforms to the standard. Mark - Bericht beantwoorden - Van: "Dimitry Sibiryakov" Aan: "For discussion among Firebird Developers" Onderwerp: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement Datum: di, mrt. 8, 2016 17:06 05.03.2016 22:28, Lester Caine wrote: > It would be nice if we did not have re-order scripts from other > databases so > NOT NULL DEFAULT '30' > has to be > DEFAULT '30' NOT NULL > in Firebird. If DY agree, I can commit this change. -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-evalFirebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
08.03.2016 19:37, Dimitry Sibiryakov wrote:
>
>> The only way
>>
>> CREATE OR ALTER SEQUENCE S;
>>
>> can be allowed is that is acts as RESTART WITH 0 INCREMENT BY 1 for
>> existing sequences.
>>
>> This way the behaviour is consistent: both CREATE and ALTER produce the
>> same result: existence of generator S with the same properties {start
>> value = 0, current value = 0, increment = 1}.
>
> But in this case behavior will be inconsistent with plain ALTER TABLE that
> doesn't
> change not mentioned attributes.
We don't have CREATE OR ALTER for tables, do we?
> I hope you won't insist that "ALTER SEQUENCE s1 INCREMENT 3" must reset value
> to 0?..
Surely not. I was speaking about CREATE OR ALTER only.
Dmitry
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Firebird limits - two different articles with different values
08.03.2016 14:57, liviuslivius wrote: > > what is the limit of rows per table - i have biggest table near 2^30 > records and i am worry if i can reach limit > what are really Firebird limits for both FB2.5 and FB3 > http://www.firebirdfaq.org/faq61/ > http://www.firebirdsql.org/en/firebird-technical-specifications/ > e.g. > table rows in first is 16G in second "> 2^40" > size of table in one is 32TB and in second is ~18TB I've recently updated the latter, so it should be more correct. Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
08.03.2016 13:33, Dmitry Yemanov wrote:
> The only way
>
> CREATE OR ALTER SEQUENCE S;
>
> can be allowed is that is acts as RESTART WITH 0 INCREMENT BY 1 for
> existing sequences.
>
> This way the behaviour is consistent: both CREATE and ALTER produce the
> same result: existence of generator S with the same properties {start
> value = 0, current value = 0, increment = 1}.
But in this case behavior will be inconsistent with plain ALTER TABLE that
doesn't
change not mentioned attributes.
I hope you won't insist that "ALTER SEQUENCE s1 INCREMENT 3" must reset
value to 0?..
--
WBR, SD.
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Bool predicate with IS and parameter
Hi *, is there a way to write a predicate with BOOLEAN column and IS (in FB3)? Something like `bool_col IS CAST(? as BOOLEAN)`? JC -- Mgr. Jiří Činčura Independent IT Specialist -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Several NOT NULL constraints for the same field
Hello, All. "create table t (a integer not null not null not null)" is a valid syntax or a bug? -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-5139) mistake in comment "can't ise MutexLockGuard here"
mistake in comment "can't ise MutexLockGuard here" -- Key: CORE-5139 URL: http://tracker.firebirdsql.org/browse/CORE-5139 Project: Firebird Core Issue Type: Bug Affects Versions: 3.0 RC2, 2.5.5 Reporter: Kovalenko Dmitry Priority: Trivial server.cpp, line 5816 "can't use MutexLockGuard here" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
06.03.2016 16:55, Dimitry Sibiryakov wrote:
>
> I think we need DE to make decision.
The only way
CREATE OR ALTER SEQUENCE S;
can be allowed is that is acts as RESTART WITH 0 INCREMENT BY 1 for
existing sequences.
This way the behaviour is consistent: both CREATE and ALTER produce the
same result: existence of generator S with the same properties {start
value = 0, current value = 0, increment = 1}.
Dmitry
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Positioned attributes in CREATE/ALTER sequence statement
05.03.2016 22:28, Lester Caine wrote: > It would be nice if we did not have re-order scripts from other > databases so > NOT NULL DEFAULT '30' > has to be > DEFAULT '30' NOT NULL > in Firebird. If DY agree, I can commit this change. -- WBR, SD. -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Firebird limits - two different articles with different values
Hi, what is the limit of rows per table - i have biggest table near 2^30 records and i am worry if i can reach limit what are really Firebird limits for both FB2.5 and FB3 http://www.firebirdfaq.org/faq61/ http://www.firebirdsql.org/en/firebird-technical-specifications/ e.g. table rows in first is 16G in second "> 2^40" size of table in one is 32TB and in second is ~18TB will be good to update this and maybe columns for server versions? regards, Karol Bieniaszewski -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-evalFirebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] BLR contexts limit
All, The good thing is that the code internals are more or less ready to work with context/stream number of any size, thanks to Claudio's refactoring. So the issue is mostly about BLR. I see two possible solutions: 1) Bump BLR version, make all context-aware verbs to generate/parse longer numbers (prefixed by counter, variable-length encoded, whatever) if new BLR version is used. Support old BLR versions, for sure (for migration, message descriptions, etc) but generate new BLR version for new objects. The major problem here is backward compatibility. BLR version 6 cannot be parsed by prior engines, so backward migration via gbak becomes impossible (at least after some metadata have been modified in FB4). Perhaps we could hack gbak to change the first byte of the every BLR stream (fix the BLR version to the older one) during restore, but the context encoding is incompatible anyway. Maybe we could teach the engine to recreate BLR based on the existing source code during restore, but (1) it gonna work only if restoring with v4 gbak, (2) source code may be missing, (3) I don't really like how it would affect the layering, (4) it gonna be slower. 2) Another solution is to keep BLR version 5 but introduce new versions of existing context-aware verbs. They will be used only for context numbers > 255. Very dumb, but simplifies backward migration. Only databases with high context numbers (read: with metadata objects re-implemented under FB4) will be impossible to migrate. I'm not sure whether we have enough BLR code space for that though. Can anyone think of any better idea? I have the former solution implemented, but maybe we could do something more clever? Dmitry -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] How to create an alternative security database during restore?
Hello, >> >> >>> Did you try to restore using an embedded connection? >> No, not embedded, but via IP. >> >> But I think it makes no difference as the error is the same when >> there is no initialized security table in the configured security >> database. >> > I can suggest you 2 immediate solutions: > - restore DB before changing databases.conf (i.e. using default security db) > - restore using embedded mode (does not need password and therefore > security db at all) > Taking into an account that databases.conf should be modified locally > and initialization of security database structures in new database > anyway requires embedded access it does not look like serious > limitation. Am I missing something? In my scenario I don't have shell access to server, onyl remote access via ssh. I've a 2.5 gbak file and a 3.0 server running. I was trying to restore the database without sysdba account and with only editing database.conf once. This is currently not possible. I'll investigate the situation a little bit further in the next days... Thanks. Björn -- Björn Reimer - RRZE -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] FYI: Announcing SQL Server on Linux - The Official Microsoft Blog
https://blogs.microsoft.com/blog/2016/03/07/announcing-sql-server-on-linux/ -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
