There are many needs: 1) Sometimes, some phones skip versions, example: if the latest software version is 6, some phones upgrade from version 4 directly to 6. So we need to track which phone upgraded to which version from which version. 2) Sometimes history helps to investigate issues that come with the version upgrades. etc.
So to maintain history we need to create version # as a node and create relationships between phone nodes and version node? On Saturday, November 15, 2014 8:46:23 AM UTC-6, Michael Hunger wrote: > > My question would be: what do you want to do with the historic information? > > Von meinem iPhone gesendet > > Am 15.11.2014 um 15:13 schrieb edo okati <[email protected] <javascript:> > >: > > I am trying to model our existing relational DB into a graph model, I have > question: How do we store the history? > > let's consider I am storing APPLE phone details like this: > > Node1: Phone(IMEI: asdaksdhkjashd) > Node2:Customer(Name: A) > Relationship between Node1 and Node2 has the following properties: (Ntwrk: > ATT, Phone # : 1313123123, current_firmware_ver: 1.1, firware_updt_date: > 01/11/2014) > > If you look at the relation properties: firmware update happened on > 01/11/2014 which means before that there was a older version, but there > could be multiple firmware updates in the past. My question is where in > this model does history could be saved? > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
