Forums

by Silver Springs ... >> Wed, 23 Aug 2000 3:36:29 GMT

Hi
Who can give me good ideas or methodolgies on archiving JADE data ?

If you have a transaction class whose instances you want to archive (say, by date range selection) then what's the best way to go about it ? To keep it simple archived data could be removed to a flat file or something i.e. inaccessible until it's restored.

But there could be loads of other classes with parent-child relationship to the transaction class and for integrity you'd need to archive off all instances in those classes with references from the transaction class. This could get messy to say the least -- especially as they in turn could have parent-child relationships to other classes etc etc.

regards

_________________________________
SilverSprings ............................... silversprings@easyliving.com

by Kevin Alcock >> Wed, 23 Aug 2000 3:53:08 GMT

You could save it as XML output.

<Order>
<LineItem>...</LineItem>
<LineItem>...</LineItem>
<LineItem>...</LineItem>
</Order>

by Iain S. Kerr >> Wed, 23 Aug 2000 3:40:03 GMT

.

You could save it as XML output.

<Order>
<LineItem>...</LineItem>
<LineItem>...</LineItem>
<LineItem>...</LineItem>
</Order>

Hi
Who can give me good ideas or methodolgies on archiving JADE data ?

If you have a transaction class whose instances you want to archive

(say,
by

date range selection) then what's the best way to go about it ? To

keep

it simple archived data could be removed to a flat file or something

i.e.

inaccessible until it's restored.

But there could be loads of other classes with parent-child relationship

to

the transaction class and for integrity you'd need to archive off all instances in those classes with references from the transaction class.

This

could get messy to say the least -- especially as they in turn could

have

parent-child relationships to other classes etc etc.

regards

_________________________________
SilverSprings ............................... silversprings@easyliving.com

by Peter Gallagher >> Wed, 23 Aug 2000 22:04:29 GMT

Why archive it at all ?

I assume that you are concerned with the amount of data that you accumulated and you want to tidy it up, or the data has no more current relevance?

I'll make another assumption, that your data that you want to archive is accessed via a collection and that collection is getting bigger, and has lots of entries of objects that are no longer relevant, however those entries are still worth keeping for possible retrieval later.

Why not keep the data where it is and create a separate collection for archived data.

e.g.
Simple class structure
Class RootObject
Class Customer

Customer has two references to RootObject
Customer.myRootObject --> inversed to RootObject.allCustomers
Customer.myRootObjectArchived --> inversed to RootObject.allArchivedCustomers

If you want to archive a customer (and all its transactions, assuming that the customer has transactions) then null then move the RootObject from one reference to the other - simple.

Benefits - You still have the data, Jade will access the data more quickly if you still have it in your database, and you can unarchive something more easily.

Costs - Haven't thought of any so far

Jade handles large databases, so having the data in your Dat files is not a burden.

Happy hunting

Peter Gallagher