Re: Changing from horizontal to single table inheritance
Re: Changing from horizontal to single table inheritance
- Subject: Re: Changing from horizontal to single table inheritance
- From: Mark Wardle <email@hidden>
- Date: Wed, 09 Oct 2013 11:03:11 +0100
| Thanks all. Alternate data stores are an intriguing idea - I already switched away from using PostgreSQL to implement SNOMED_CT in favour of Lucene as the free text searching was too slow with PostgreSQL. That said, it is nice that some of the data collection forms have relational constraints to other parts of the patient record.
Good to think about this, but I think I'll park the ideas for now. Only issue is keeping a hand on performance metrics and considering again if we do hit a problem.
Best wishes,
Mark On 6 Oct 2013, at 21:02, Kieran Kelleher < email@hidden> wrote: Might be worth checking a Graph Database such as Neo4j as a possible solution for your domain model requirements.
On Oct 6, 2013, at 2:08 PM, Ramsey Gurley < email@hidden> wrote: You need a schema-less approach if you need to create these things at runtime. Relational databases really aren't such a good fit in these cases. You can shoe horn something into a RDBMS with EAV or datablobs, but it won't scale well.
If you're using Postgres 9.2.x or better, there is built in JSON data storage you could use. You can write stored procedures using PLV8, an embedded V8 _javascript_ engine. It's also <flamebait>faster than MongoDB</flamebait> based on what I've read.
-- Dr. Mark Wardle Consultant Neurologist, University Hospital Wales, Cardiff, UK Email: email@hidden or email@hidden Twitter: @mwardle Telephone: 02920745274 (secretary) or facsimile: 02920744166
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden