Hi Dexter; I think we will be doing both : storing binary files as blobs and some of property files as documents. Lets say you have existing property file which you want to load into database. Do you load it as a Document record or Graph? I tried to load it as Document record and it seems that I would need to generate ODocument for each property? Basically one property file will be stored as a collection of ODocument records. Is that correct assumption? Did you find any build in libraries to do that or it is just - open the file, read line by line, generate ODocument, doc.save() ?
Thank you. On Tuesday, April 1, 2014 10:36:54 AM UTC-7, Dexter Pratt wrote: > > Hi Galina, > > are you trying to store the configuration information in ways that you can > reason on it - i.e. to "look inside" the artifacts that you store? > > Or do you just want to retrieve the files again? > > In my project, we are going to considerable effort to parse various kinds > of source documents into objects in a common schema and store them - > because we want to enable queries into those objects by users. > > But if I only wanted to hand back the original file at query time, I'd > just store the file as a blob or even just use a file system and manage the > metadata in a db. > > - Dexter > > Dexter Pratt > Director, NDEx project > Ideker Lab UCSD / Cytoscape Consortium > [email protected] <javascript:> - [email protected] <javascript:> > www.ndexbio.org > > On Tuesday, April 1, 2014 at 10:22 AM, galina wrote: > > I am new to OrientDB. I am trying to use OrientDB from Java to store > different types of configuration files in our system. The goal is to be > able to store and quickly retrieve XML files, property files, CSV files, > binary files. I am guessing that Document DB approach would work for that? > Does OrientDB has any build in libraries to load CSV files, or XML files > into database? I know how to read, for example, CSV file line by line and > create ODocument and store it. Is there better way to do it? What about XML > files? What is the best approach to design database for storing different > types of documents? > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" 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 "OrientDB" 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.
