-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
simplify id types and related stuff #49
base: master
Are you sure you want to change the base?
Conversation
Conflicts: src/main/scala/com/bio4j/dynamograph/model/go/TableGoSchema.scala
…raph into refactoring/recomendations
Hey @eparejatobes I stuck - I do not see any progress in my work - and what is worse I do not know what to do in order to solve those problems :( |
OK let me see, don't worry :) |
Yes I know but I feel ashamed - I constanlty asking you for help, I waste a lot of time trying to make any progress and what is more we set today as coding deadline but If all those problems with types etc will no be resolved I do not manage :( I really want to but probably I am too stupid |
No problem @alberskib all this was in the project description, this is pretty hard (I mean the types part) and it was expected that you would need help with it. Actually I assumed that I'd need to put more time on this kind of things! Let me take a calm look at it and I'd come up with something. |
If at first glance you see anything that could help please write it - I will also try to investigate but without any hint I do not know how to continue |
I'd start with getting rid of dao, and implementing all the reading from the db inside vertex/edge. Require an implicit of vertexTable/edgeTables in the corresponding implicit methods |
hey @alberskib I need to check some things, better to meet tomorrow |
OK 5PM tommorow |
I'll be working on this branch, just in case |
I will more or less concurrently work in old branch (refactoring/recomendations) |
No description provided.