I have a question regarding the object oriented database and object
oriented database management systems with regards to Ruby.
My question is this: is there a pure object oriented database and
management system to use with Ruby or is a common practice to use the
ORM to interface with relational databases?
I need to design data models for an application as a part of my thesis
and I wanted to go object oriented in all aspects.
I would really appreciate if someone can shed some light on the subject
or suggest some reading. I've been reading online and in books about it,
but I'm experiencing the "more I read the less I know" effect:(
It comes down to the question whether it is possible to use in practice
Ruby with OODB and OODBMS without an ORM. If that is not possible I
should probably go from pure object data model to object relational data
model design...
My question is this: is there a pure object oriented database and
management system to use with Ruby or is a common practice to use the
ORM to interface with relational databases?
From what I am reading I gather it's the latter.
I need to design data models for an application as a part of my thesis
and I wanted to go object oriented in all aspects.
I would really appreciate if someone can shed some light on the subject
or suggest some reading. I've been reading online and in books about it,
but I'm experiencing the "more I read the less I know" effect:(
It comes down to the question whether it is possible to use in practice
Ruby with OODB and OODBMS without an ORM.
Personally I am not aware of any OODB which can be used with Ruby. The
typical use case seems to include ORM with RDBMS.
If that is not possible I
should probably go from pure object data model to object relational data
model design...
Depending on the use case (e.g. if your data volume is small) you can also
use Marshal which is a form of serialization - or PStore.
Kind regards
robert
···
On Wed, Aug 21, 2013 at 10:08 AM, Sebastjan H. <lists@ruby-forum.com> wrote:
Here is a bit more info on my question. I'm preparing an analysis of
information requirements for a specific company which would in fact
result in a sort of a blueprint for an ERP application for this micro
scale company. I'd like for this analysis to be a plausible blueprint
for programming if so decided and not just something theoretical. I
won't be programming it myself as this is far beyond my experience and
knowledge.
So far I've used PStore and YAML::Store in my smaller learning apps. For
this ERP I think I need to choose something different though. Again, I
need the theoretical blueprint which can be used in practice.
Furthermore, I've just realized if this would be executed in a web app,
Rails is most probably the answer and as such ActiveRecord is in place.
So far I've analyzed the organizational and other structures as well as
the business processes of the company. Based on that I now need to move
to the system requirements and data modeling. And I'm stuck here because
of the OODBMS question. My fear is that if I go with pure object
modeling supposing the OODBMS it wouldn't be executable in practice.
Furthermore, I've just realized if this would be executed in a web app,
Rails is most probably the answer and as such ActiveRecord is in place.
Right, and that's probably your most "plausible blueprint"
So far I've analyzed the organizational and other structures as well as
the business processes of the company. Based on that I now need to move
to the system requirements and data modeling. And I'm stuck here because
of the OODBMS question. My fear is that if I go with pure object
modeling supposing the OODBMS it wouldn't be executable in practice.
I don't see why the choice of persistence mechanism would have
any significant effect on your data modeling. But maybe I haven't
thought it through sufficiently
Best of luck,
H*
···
On Wed, Aug 21, 2013 at 8:35 AM, Sebastjan H. <lists@ruby-forum.com> wrote:
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
I'd rather use an ORM with a RDBMS - simply because data in a RDBMS is
usually well accessible and there are a lot tools for manipulation and
reporting based off a RDBMS. Meanwhile there may be equally good tools for
ODB - but I doubt it.
Kind regards
robert
···
On Wed, Aug 21, 2013 at 5:35 PM, Sebastjan H. <lists@ruby-forum.com> wrote:
Thank you, Hassan and Robert.
Here is a bit more info on my question. I'm preparing an analysis of
information requirements for a specific company which would in fact
result in a sort of a blueprint for an ERP application for this micro
scale company. I'd like for this analysis to be a plausible blueprint
for programming if so decided and not just something theoretical. I
won't be programming it myself as this is far beyond my experience and
knowledge.
I don't see why the choice of persistence mechanism would have
any significant effect on your data modeling. But maybe I haven't
thought it through sufficiently
you're right. For the purpose of design and data modeling it doesn't
matter what persistence mechanism would be chosen later on. I'll go with
the object data model.
