[
https://issues.apache.org/jira/browse/DERBY-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633157#comment-13633157
]
Tony Brusseau edited comment on DERBY-6135 at 4/16/13 6:47 PM:
---------------------------------------------------------------
No, the id's never start anywhere near 0. The upper 8 bits of the long is used
to represent type info (this allows me to have unique ids across multiple
tables while still using sequences for id generation), and the numbers grow
normally from there. So the upper byte and lower 3-4 bytes always have relevant
data bits set.
was (Author: apb):
No, the id's never start anywhere near 0. The upper 8 bits of the long is
used to represent type info, and the numbers grow normally from there. So the
upper byte and lower 3-4 bytes always have relevant data bits set.
> Request data compression scheme (i.e., gzip of data pages)
> ----------------------------------------------------------
>
> Key: DERBY-6135
> URL: https://issues.apache.org/jira/browse/DERBY-6135
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Reporter: Tony Brusseau
>
> This is a request for a data compression scheme facility added to Derby
> (something like gzip of data pages). MySQL and some other databases provide
> such a feature, see:
> http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-compression-internals.html
> The desire for this is because my current database size is 27GB but gzipped,
> it goes down to 7GB. I wish to scale my database dramatically, but the
> current disk footprint would prevent me from being able to use Derby.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
