> On Oct 15, 2015, at 7:11 AM, Holly M. <[email protected]> wrote: > > Hello everyone, > > I am in the modeling phase of a project using Neo4J as a storage-backend. > The data I want to store is in form of a graph, so a graph database was the > first choice. > > But now I'm running into problems modeling the data structure. > > In some cases I have to store whole files or documents. They are of different > shape and format (xml, object files, .sh, .f etc) > and have nearly arbitrary length. > I want these datasets within my graph (or at least a reference for them or > something) > > It will not be necessary to search within the files a lot, but its important > to find the files themselves when needed. > > Now is my question: What is a recommended way of storing files or documents > within graph database Neo4J? > > Can I get them in a special labled node, or do I have to use references and > another storing system just for the files to find them again? > Are there other possibilities of solving this problem?
What are your requirements in terms of atomicity? Will the files and their relationships be changing often? Do you need to be able to “ship” the database around? Sean -- 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
