I'm reading the Firebird Internals pdf documentation and feel puzzled about the
encoding of two repeating bytes.
You may have noticed that the two consecutive characters 'DD' did not get
compressed. Compression only takes place when there are three or more identical
characters.
Indeed the pdf
It was probably written in the sky that I had to post a typo, but I did it.
Why isn't this encoded as {ff 44} which is not shorter than the initial data,
but at least is not larger.
Read this {fe 44} for minus 2 followed by 44.
But the question remains open, I still do not get why 'DD'
On 01/02/12 09:36, Olivier Mascia wrote:
I'm reading the Firebird Internals pdf documentation and feel puzzled about
the encoding of two repeating bytes.
You may have noticed that the two consecutive characters 'DD' did not get
compressed. Compression only takes place when there are three
On 01-02-2012 09:35, Norman Dunbar wrote:
PS. One day I'll finish decoding the internals and finish the manual!
Thanks for reading so far.
You're manual is very great. I'm able to read (kind of) table data based
only on it (didn't even looked at FB sources).
Adriano
On 01/02/12 13:35, Adriano dos Santos Fernandes wrote:
You're manual is very great. I'm able to read (kind of) table data based
only on it (didn't even looked at FB sources).
Thanks!
Cheers,
Norm.
--
Norman Dunbar
Dunbar IT Consultants Ltd
Registered address:
Thorpe House
61 Richardshaw Lane
database file appears corrupt only on some computers
Key: CORE-3749
URL: http://tracker.firebirdsql.org/browse/CORE-3749
Project: Firebird Core
Issue Type: Bug
Components: API /
31.01.2012 2:12, Adriano dos Santos Fernandes wrote:
There is two obscure SQL commands called READ BLOB and WRITE BLOB.
The idea behind these commands is to make blob read/write using the
cursor (fetch/insert) API. Why they exist is not something I know, maybe
it predates blob API functions?
On 01-02-2012 12:46, Dmitry Yemanov wrote:
31.01.2012 2:12, Adriano dos Santos Fernandes wrote:
There is two obscure SQL commands called READ BLOB and WRITE BLOB.
The idea behind these commands is to make blob read/write using the
cursor (fetch/insert) API. Why they exist is not something I
Здравствуйте, Jilles.
Вы писали 28 января 2012 г., 20:24:07:
[stuck process cannot be killed, system hangs when reboot is
attempted]
JT A signal cannot forcibly kill a process that is stuck in the kernel.
JT Allowing this would put the integrity of the kernel data structures at
JT risk and
