Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Storing header information to database
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Amergin  
View profile  
 More options Jul 24 2012, 9:29 am
From: Amergin <amergi...@gmail.com>
Date: Tue, 24 Jul 2012 06:29:46 -0700 (PDT)
Local: Tues, Jul 24 2012 9:29 am
Subject: Storing header information to database

I've a database where the graph represents a single dataset. Every node has
multiple attributes, among one of them is a list of datapoints, and the
list is stored as a single string, for example:

"-0.145612:-0.017787:-0.149197:0.019434:-0.030675:-0.018852:-0.059626:-0.12 3525:-0.085181:-0.095958:0.070881:-0.068942:-0.011469:-0.131096:-0.145013:- 0.220525:-0.083212:0.012034:-0.040449:0.065762:-0.188752:0.002856:-0.059711 :-0.012304:-0.106168:-0.088554:-0.024919:-0.211156:-0.077468:-0.077814:-0.0 99627:0.062143:-0.037822:-0.003117:0.119588:-0.321827:0.146043:0.018319:-0. 116253:0.063670:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA :NA:NA:NA"

Every datapoint originates from a single source, for example the first
datapoint could be from source1, second from source2 etc. These are all
identical for the nodes.

Now the question is, how should this source information be stored in the
database?
- Every node could have an attribute containing a list of the sources. I
would then, however, wasting space since they are identical for all the
nodes.
- I could create a single node that contains these, and link the node to
every real data node. This doesn't seem very handy since if I want to
access the sources directly I'd need to remember the node number or create
an index containing the one node and do a wildcard query to it (which,
according to the documentation is not advisable).


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Michael Hunger  
View profile  
 More options Jul 24 2012, 6:22 pm
From: Michael Hunger <michael.hun...@neotechnology.com>
Date: Tue, 24 Jul 2012 23:22:25 +0100
Local: Tues, Jul 24 2012 6:22 pm
Subject: Re: [Neo4j] Storing header information to database
What about creating one node per data source and relating your nodes to the datasource and putting the actual value as property on the relationship?

Michael

Am 24.07.2012 um 14:29 schrieb Amergin:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »