-
Notifications
You must be signed in to change notification settings - Fork 1
Create Application collection and fill it with mock applications #10
Comments
i think you would want to have those two subclasses for sorting. |
@jaylenw monetary donation and computer requests are already in two different tables. What exactly are you talking about? |
@djblanc360 @nguym077 Still trying to figure out how to make this work with OrientDB. I could be totally wrong with this but would it work to have two application tables, one for donations and one for requests? That way we dont have to worry about doing a "join" of applications and donation and of application and request. So instead of three tables, there would be two. I am not sure. I think we should aim for what it is now in the diagram of having three tables and "join" the donation and request tables with applications for the user. We just need to figure out how to do a join with Baasbox and OrientDB. |
@jaylenw well the "proper" way to do it would be to make it a subclass but you can do it however you want to do it. Having two application tables would be repetitive since they're both going to have the same information on them. Also, it'd get a lot messier since officer's pk will be copied into each application table and user's pk would also need to be copied over into each application table. That's just poor design. |
hmm I was just looking through the mysql stuff I was working on before we decided to do baasbox and there is no way we are getting around not using a "join". we can't do joins in orientDB? @jaylenw |
@nguym077 correct no way to do a join like we are used to in sql but it seems OrientDB supports "sql" like operations in its own way. That is why i was all torn on how to do the tables now since we switched to baasbox. Check this out on the Joins section https://orientdb.com/docs/2.2/SQL.html. Also, baasbox seems like it allows us to do queries in the URL like this http://opensource.baasbox.com/documentation/0.9.5/#geospatial-queries |
Create a copy of the documents in applications and save it in the repo as a json file.
The text was updated successfully, but these errors were encountered: