On 01/15/2017 07:26 PM, Alex Peshkoff wrote:
> On 01/15/17 12:24, Damyan Ivanov wrote:
>> -=| Alex Peshkoff, 13.01.2017 14:32:09 +0300 |=-
>>> On 01/03/17 00:38, Damyan Ivanov wrote:
I've been chasing this for some time, and finally I've come (with help
from others) to a environment which
Hi,
http://www.firebirdsql.org/en/snapshot-builds/
or
you can build it from code
https://github.com/FirebirdSQL/firebird/commits/B3_0_Release
regards,
Karol Bieniaszewski
W dniu 2017-01-16 11:40:23 użytkownik Stephan Bergmann
napisał:
> On 01/15/2017 07:26 PM, Alex Peshkoff wrote:
> > On 01/15
On 01/16/2017 02:18 PM, liviuslivius wrote:
> http://www.firebirdsql.org/en/snapshot-builds/
> or
> you can build it from code
> https://github.com/FirebirdSQL/firebird/commits/B3_0_Release
Ah, I was looking/hoping for a reasonably small and self contained
source code patch that I could apply to
INSERT into updatable view without explicit field list failed
-
Key: CORE-5454
URL: http://tracker.firebirdsql.org/browse/CORE-5454
Project: Firebird Core
Issue Type: Bug
here it is
https://github.com/FirebirdSQL/firebird/commit/40f782ae3e918c4f3842571ff8064be1c4f54961
same in debian git
https://anonscm.debian.org/cgit/pkg-firebird/3.0.git/commit/?id=84021ce684210475ec44f6c3e7a8fc04c612b5a0
On Mon, Jan 16, 2017 at 3:49 PM, Stephan Bergmann
wrote:
> On 01/16/20
16.01.2017 15:49, Stephan Bergmann wrote:
> On 01/16/2017 02:18 PM, liviuslivius wrote:
>> http://www.firebirdsql.org/en/snapshot-builds/
>> or
>> you can build it from code
>> https://github.com/FirebirdSQL/firebird/commits/B3_0_Release
>
> Ah, I was looking/hoping for a reasonably small and self
On 01/16/17 13:40, Stephan Bergmann wrote:
> On 01/15/2017 07:26 PM, Alex Peshkoff wrote:
>> On 01/15/17 12:24, Damyan Ivanov wrote:
>>> -=| Alex Peshkoff, 13.01.2017 14:32:09 +0300 |=-
On 01/03/17 00:38, Damyan Ivanov wrote:
> I've been chasing this for some time, and finally I've come (w
15.01.2017 19:00, Adriano dos Santos Fernandes wrote:
> So what I call virtual metadata and how would it solve the problems:
>
> When a DDL command is issued, it will not change metadata directly. It
> will change metadata in a memory structure tied to the current transaction.
>
> It may read metad
On 01/15/17 18:32, Dmitry Yemanov wrote:
> 15.01.2017 17:50, Adriano dos Santos Fernandes wrote:
>
>> What is our maximum code right margin?
>>
>> AFAIK it used to be 100 and I remember some discussion to increase it.
>>
>> Some people is thinking it's infinite.
>>
>> I think currently 100 is too l
16.01.2017 19:39, Alex Peshkoff wrote:
>
> With today 22-24" 16:9 screens
20" 4:3 is still enough for me ;-)
Dmitry
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org!
On 01/16/17 19:58, Dmitry Yemanov wrote:
> 16.01.2017 19:39, Alex Peshkoff wrote:
>> With today 22-24" 16:9 screens
> 20" 4:3 is still enough for me ;-)
A few years ago I had to replace my old Sun tube cause it stopped to
work. I wanted to buy 4:3 monitor but there was nothing available with
app
On 16/01/2017 14:39, Alex Peshkoff wrote:
> On 01/15/17 18:32, Dmitry Yemanov wrote:
>> 15.01.2017 17:50, Adriano dos Santos Fernandes wrote:
>>
>>> What is our maximum code right margin?
>>>
>>> AFAIK it used to be 100 and I remember some discussion to increase it.
>>>
>>> Some people is thinking
On 01/15/17 21:00, Adriano dos Santos Fernandes wrote:
> All,
>
> First, must say this is based on state-of-the-art modern architecture of
> a different field: web libraries/frameworks, using the Virtual DOM.
>
> First, the (Firebird) problem, but I'll abstain to comment internal
> details of DFW.
On 01/16/17 20:19, Adriano dos Santos Fernandes wrote:
> PS: finally receiving your emails again
>
Nice to know, hope big guys in mail.ru / google solved some problems.
--
Check out the vibrant tech community on one of
On 16/01/2017 15:40, Alex Peshkoff wrote:
> On 01/15/17 21:00, Adriano dos Santos Fernandes wrote:
> I like the suggestion in general but some details worth thinking more.
Sure. It's yet more an general idea than a proposal.
What I like about it, it's much simple in relation to what we have now
w
15.01.2017 21:49, Dimitry Sibiryakov wrote:
>
>> When a DDL command is issued, it will not change metadata directly. It
>> will change metadata in a memory structure tied to the current transaction.
>
> I would prefer other approach: DDL command change metadata in database
> directly and
> immedia
16.01.2017 19:42, Dmitry Yemanov wrote:
> But I fail to see how these ideas are
> going to work for table format changes. How would records be stored
> accordingly to the "virtual" formats? How are formats going to be
> uniquely (but without gaps!) numbered across uncommitted transactions?
Why
16.01.2017 22:04, Dimitry Sibiryakov wrote:
>
> Why "without gaps"? In my vision the first step is to modify garbage
> collector/sweeper
> to clean unused formats out.
OK, it wasn't obvious from your message.
>> How concurrent readers should access/skip physically stored records if
>> their form
16.01.2017 20:23, Dmitry Yemanov wrote:
> But what about low-level logic like
> VIO_get_current() which must see uncommitted changes?
If format is created at the end of DDL execution (instead of DFW), it
can/must be
written into database before any DML can write any record with new format.
Em 16/01/2017 16:42, Dmitry Yemanov escreveu:
> 15.01.2017 21:49, Dimitry Sibiryakov wrote:
>>
>>> When a DDL command is issued, it will not change metadata directly. It
>>> will change metadata in a memory structure tied to the current transaction.
>>
>> I would prefer other approach: DDL command
Dne 16. 1. 2017 v 18:13 Alex Peshkoff napsal(a):
> A few years ago I had to replace my old Sun tube cause it stopped to
> work. I wanted to buy 4:3 monitor but there was nothing available with
> appropriate matrix (can't work with something worse than IPS/SFT -
> problem with eyes). I could not f
16.01.2017 21:08, Adriano dos Santos Fernandes wrote:
> DML changes in the same transaction uses real metadata, i.e., DDL being
> changed does not affect DML or metadata cache.
>
> Virtual metadata is specific to DDL.
>
> Record format will be generated when applying the changes in commit.
Then
Em 16/01/2017 18:39, Dimitry Sibiryakov escreveu:
> 16.01.2017 21:08, Adriano dos Santos Fernandes wrote:
>> DML changes in the same transaction uses real metadata, i.e., DDL being
>> changed does not affect DML or metadata cache.
>>
>> Virtual metadata is specific to DDL.
>>
>> Record format will
16.01.2017 21:52, Adriano dos Santos Fernandes wrote:
> It wasn't in my requirements, but it would be possible.
>
> create table ...
> as
> select ...
>
> Would run the select and fill the table at commit time.
Oh, then I misread your suggestion. I read it as "let's create table/view/sp
in mem
Em 16/01/2017 18:58, Dimitry Sibiryakov escreveu:
> 16.01.2017 21:52, Adriano dos Santos Fernandes wrote:
>> It wasn't in my requirements, but it would be possible.
>>
>> create table ...
>> as
>> select ...
>>
>> Would run the select and fill the table at commit time.
>
>Oh, then I misread yo
16.01.2017 22:26, Adriano dos Santos Fernandes wrote:
> The semantics of this is even unthinkable, and I doubt anyone is doing
> it in database world.
PostgreSQL does IIRC.
--
WBR, SD.
--
Check out the vibrant te
DefaultDbCachePages seems ignored
--
Key: CORE-5455
URL: http://tracker.firebirdsql.org/browse/CORE-5455
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0.2
Em 16/01/2017 19:42, Dimitry Sibiryakov escreveu:
> 16.01.2017 22:26, Adriano dos Santos Fernandes wrote:
>> The semantics of this is even unthinkable, and I doubt anyone is doing
>> it in database world.
>
>PostgreSQL does IIRC.
>
>
Seems to allow to insert data after DDL in the same trans
16.01.2017 23:08, Adriano dos Santos Fernandes wrote:
>
> DML changes in the same transaction uses real metadata, i.e., DDL being
> changed does not affect DML or metadata cache.
I.e. one cannot add a field and populate it with data within a single
transaction. This sounds too much restrictive.
16.01.2017 23:39, Dimitry Sibiryakov wrote:
> Then your schema won't solve problem with mixing DDL and DML. Users still
> won't be able
> to create table and fill it with data in one transaction.
How does your idea address this? Between CREATE TABLE and INSERT page
space (PP, IRP) must be alloc
16.01.2017 22:48, Dimitry Sibiryakov wrote:
>
>> But what about low-level logic like
>> VIO_get_current() which must see uncommitted changes?
>
> If format is created at the end of DDL execution (instead of DFW), it
> can/must be
> written into database before any DML can write any record with new
Yet another case:
Transaction creates a new format, stores some records using this new
format, then the server dies. After restart, changes in
RDB$FORMATS/RDB$RELATIONS are occasionally backed out. Then it could be
impossible to garbage collect the new record versions due to their
format being
Migrating Firebird 2.5.2 to 3.0.1 gbak restore crashes at the end always
Key: CORE-5456
URL: http://tracker.firebirdsql.org/browse/CORE-5456
Project: Firebird Core
Issu
33 matches
Mail list logo
