Manually defining store history

[Matt Cordell]

It seems brightstar uses the actual/real commit time to identify the various historical states of a store.

I have some existing data, that has been developed using an append only method also that I'd like to import into a brightstar store.

Assuming I've broken up the existing data into each of it's historical deltas. (let's say they happened on the 1st of each month).

I was hoping to import each 'monthly delta' as it's own transaction, but keep the respective 'versions'

So

Rather than 

November 11 2014 09:20

November 11 2014 09:22

November 11 2014 09:24

...

I'd like to have something like

March 2012

April 2012

May 2012

...

I appreciate I might need to modify my existing version formats. But is it possible to specify a specific value for 'commit time' for when I call ExecuteTransaction() ?

Thanks in advance.

Matt

[Khalil Ahmed]

Hi Matt,

Firstly, please use the Codeplex discussion forum [1] for questions - this forum is deprecated and it would be good to have questions like this recorded in the active dicussion forum.

Anyway to answer your question, the short answer right now is "No" :-( It is not possible to override the transaction timestamp through options to ExecuteTransaction(). I'm not sure it would be right to override the transaction timestamp, however it feels like it might be a nice feature to enable transactions to be "tagged" in some way to allow you to find a particular transaction by its tag - I'll log that as a possible future feature.

Just to probe a little into your use case - is this just to use the transaction information as a way of storing a bit of historic state about the data? Or are you looking to use the historical deltas as a way to control what information is returned by a query (by selecting a particular commit point to query) ? Do you have any date / time information in the data itself ? I'm just wondering if it might be an idea to use separate graphs for each snapshot or to track the deltas in some other way inside the data itself, but the precise approach might depend somewhat on your particular use case.

Cheers

Kal

[1] http://brightstardb.codeplex.com/discussions

--
You received this message because you are subscribed to the Google Groups "BrightstarDB Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brightstardb-us...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kal Ahmed
Director, Networked Planet Limited
e: kal....@networkedplanet.com
w: www.networkedplanet.com

[Matt Cordell]

Thanks. I thought I had seen somewhere that questions be posted there (However this page still links to the google groups - http://brightstardb.readthedocs.org/en/latest/Getting_Support/)

(There's some much more useful thread over on codeplex too :D)

Thread started here -

Thanks.

[Khalil Ahmed]

Thanks for the heads-up on that Matt - I've patched the docs in GH so the develop branch is updated and latest will get patched when the 1.8 release goes out.

Cheers

Kal

--
You received this message because you are subscribed to the Google Groups "BrightstarDB Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brightstardb-us...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.