Skip to content
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

move to schema model #34

Closed
madibalive opened this issue Jan 22, 2019 · 4 comments
Closed

move to schema model #34

madibalive opened this issue Jan 22, 2019 · 4 comments

Comments

@madibalive
Copy link

Hi i have started updating my local copy with features, would push when stable , but biggest issue i have is the cezerin original lack mongo db schema ?? is there is reason you guys are sticking to no schema model, i was wondering if you where open to schema modules, allows to switching out database , am currently using mysql with sequilize as orm, fairly straight forward , using global search for collection keyword and modifying each code to use the sequilize ?

@neunygph
Copy link
Contributor

Why is it an issue for you, MongoDB is a schemaless database, it makes it flexible to update and add new fields.

@madibalive
Copy link
Author

my issue is that most mongodb project i have worked on, or most opensourced project using mongodb tends to have a schema model which allows for hooks (before and after save,update,create ... ),
was wondering if there is reason your guys sticking to no schema model, or would be entertain moving to a mongodb schema model?

@lfurzewaddock
Copy link

Consider postgreSQL. JSONB column datatype can be used when neccessary for migration from mongoDB.

@ngoyal16 ngoyal16 added this to To do in v1.0 Feb 18, 2019
@github-actions
Copy link

github-actions bot commented Jun 3, 2020

Stale issue message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
v1.0
  
To do
Development

No branches or pull requests

3 participants