Mailing-List: contact commits-help@empire-db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@empire-db.apache.org
Date: Sun, 22 Jul 2012 19:39:33 +0000 (UTC)
From: =?utf-8?Q?Rainer_D=C3=B6bele_=28JIRA=29?=
 <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Message-ID: <1872821678.88485.1342985974351.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <2023583170.11564.1334136029211.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (EMPIREDB-138) Optimize serialization by making
 database and rowset references transient
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/EMPIREDB-138?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rainer D=C3=B6bele closed EMPIREDB-138.
----------------------------------

    Resolution: Fixed
   =20
> Optimize serialization by making database and rowset references transient
> -------------------------------------------------------------------------
>
>                 Key: EMPIREDB-138
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-138
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rainer D=C3=B6bele
>            Assignee: Rainer D=C3=B6bele
>
> Serialization of Column or Rowset will currently require the entire datab=
ase to be serialized.
> Making references to the database and rowset transient will significantly=
 reduce the amount of storage required.
> However this requires custom serialization and desericalization as well a=
s a mechanism to identify a database object instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira