I was going over https://software-lab.de/doc/tut.html#db and looks like I should just go with the Entity/Relation model. Thanks Alex.
On Tue, Apr 16, 2019 at 10:15 PM Alexander Burger <a...@software-lab.de> wrote: > On Tue, Apr 16, 2019 at 03:57:14PM -0700, C K Kashyap wrote: > > Thanks Joh-Tob, > > I think properties work for me. I was thinking that symbol would map to > > "key" but that need not be the case. My goal is to figure out a way to > > store records that are 4 tuple - "Entity name", "Attribute", "Value", > > "TimeStamp/TransactionID" (just like datomic). What do you recommend? > > If you don't have just simple key/value pairs, you better go with an > Entity/Relation model, and store arbitrary data in objects. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
