Em 04/03/2016 13:37, Michal Kubecek escreveu:
> On Fri, Mar 04, 2016 at 04:53:47PM +0100, Philippe Makowski wrote:
>>
>> just for information here the log of the attempt to build Firebird 3.0
>> RC2 under Fedora RawHide (gcc 6.0.0)
>>
>>
Hi,
to be able to do it, I need to switch to record level compression.
And for this task I need your help.
For first, you can use a memory move instead compression, I will replace
by ELekt Labs RLE (+LZ4) for fist iteration.
Next I will change to value encoding or value encoding + LZ4 (or LZ4
04.03.2016 18:49, Slavomir Skopalik wrote:
>
> if you help me with integration, will do it.
I will. Just consider it a trial development. I cannot promise anything
before seeing the test results.
Dmitry
--
Compiler issues message about "invalid request BLR" when attempt to compile
wrong DDL of view with both subquery and "WITH CHECK OPTION" in its DDL
---
Hi Dmitry,
if you help me with integration, will do it.
Slavek
> I have nothing against a value-based encoding. But our v4 development
> tasks currently do not include inventing one. If someone jumps in with a
> prototype implementation, I'd be definitely willing to review/consider it.
>
>
>
03.03.2016 22:49, Slavomir Skopalik wrote:
>
> Is it right time or will be postponed to V5
So far I see no serious reason to postpone it. Just please wait a couple
of weeks, I will post to this thread when ready.
Dmitry
03.03.2016 19:52, James Starkey wrote:
>
> I was not talking about value-based encoding (which surely requires a
> different approach).
>
> And why not?
I have nothing against a value-based encoding. But our v4 development
tasks currently do not include inventing one. If someone jumps in
FB 3 RC2 installer is displaying "empty texts" when Portuguese is selected
--
Key: CORE-5129
URL: http://tracker.firebirdsql.org/browse/CORE-5129
Project: Firebird Core
Allow to specify a prefix protocol for embedded
---
Key: CORE-5128
URL: http://tracker.firebirdsql.org/browse/CORE-5128
Project: Firebird Core
Issue Type: Improvement
Reporter: Simonov
On 03/03/16 20:13, Jim Starkey wrote:
>> Where i can see a useful segregation is archival data which will never
>> be modified. Would be very usefull if all that could be backed up on a
>> Slow cycle, and only the real dynamic data kept in the primary table
>> space? But one can do most of that by
10 matches
Mail list logo
