[ https://jira.fiware.org/browse/HELP-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Lopez deleted HELP-13388: ---------------------------------- > [fiware-stackoverflow] FIWARE Orion and user data management vs mysql database > ------------------------------------------------------------------------------ > > Key: HELP-13388 > URL: https://jira.fiware.org/browse/HELP-13388 > Project: Help-Desk > Issue Type: Monitor > Reporter: Backlog Manager > Labels: fiware, fiware-orion > > Created question in FIWARE Q/A platform on 25-03-2015 at 02:03 > {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/29245736/fiware-orion-and-user-data-management-vs-mysql-database > +Question:+ > FIWARE Orion and user data management vs mysql database > +Description:+ > I was asked to create a backend server for storing and managing user information data, specifically using Orion Context Broker. How can Orion help me avoid using my own database (for example a local sql)? I'm new to FIWARE Orion, and as far as I've read in the manuals, I can create entities and attributes associated with them, something amazing when using node-like entities such as sensors. But how can I store information about many authenticated users if it's mandatory to have a parent-child entity relation like this: > user 1 -> car 1 -> cylinder 1 -> tempCyl.. Can I refer to "tempCyl" with only one request? Or is it mandatory to chain requests (for example set attribute child "tempCyl" to "cylinder 1" and vise-versa? > Also if under "user 1" entity, the information is sensitive, is there a way to protect data with a valid token (like OAuth for example)? Or do I have to create my own internal (non internet accessible) Orion instance? -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy