Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Implement Doctrine2 #16

Closed
rmburkhead opened this issue Dec 29, 2011 · 5 comments
Closed

Implement Doctrine2 #16

rmburkhead opened this issue Dec 29, 2011 · 5 comments
Assignees
Milestone

Comments

@rmburkhead
Copy link
Member

Update the module to be database-driven, rather than hard-coding document types and managing dynamic elements in module variables.

@ghost
Copy link

ghost commented Dec 29, 2011

See #15, all modules should be written for Doctrine 2.

@rmburkhead
Copy link
Member Author

Regarding the discussion over on issue #15, so the only question, then, is whether this should be implemented in Legal module version 2.0.x or 3.0.0.

Database-driven now or later?

@ghost
Copy link

ghost commented Dec 29, 2011

That's up to you :-)

@craigh
Copy link
Member

craigh commented Jan 10, 2014

I need to understand what exactly needs to be done here. I don't understand the initial premise. What needs to be stored and why? I can probably do the work, I just need to understand.

@craigh craigh modified the milestone: 3.0.0 Aug 27, 2016
@Guite Guite self-assigned this Oct 15, 2016
@Guite
Copy link
Member

Guite commented Oct 21, 2016

I am about to close this, as I do not see the need for having a dedicated database tables for these few module vars. This would just increase complexity imo. Feel free to reopen if you have any objections about this decision.

@Guite Guite closed this as completed Oct 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants