Hey guys. Im looking to make a model with fewer included modules from
ActiveRecord. Basically, i want to include only the modules so it can
work
fine inside rails and with the methods to access the database.
I tried to do it by myself, but i could make it work.
Which modules should i include to reach my needs?
On Friday, 22 March 2013 09:56:23 UTC-4, Paulo R. wrote:
Hey guys. Im looking to make a model with fewer included modules from
ActiveRecord. Basically, i want to include only the modules so it can work
fine inside rails and with the methods to access the database.I tried to do it by myself, but i could make it work.
Which modules should i include to reach my needs?
You’ve explained what you’re trying to do, but not why - explaining
why
you want to do this might make it easier to figure out how to make it
happen.
–Matt J.
Thx for your reply. I want to make the models more light. I want to make
models what will only access the database (CRUD), without callbacks and
the
other stuffs it loads.
Em sbado, 23 de maro de 2013 12h19min06s UTC-3, Matt J. escreveu:
Em segunda-feira, 25 de maro de 2013 14h39min09s UTC-3, Matt J.
escreveu:
Not to be rude, but this is still “what” you want to do.
Why are you trying to make the models “light”? Are you working in a
resource-constrained environment? Splitting off the callback system is
going to break plenty of stuff - for instance, :dependent => :destroy on
associations is implemented with a callback. Would it be sufficient to
simply not use features you don’t want?–Matt J.
Im trying to make my own solution. Instead of working with MVC, im
working
with another patterns as well. And i want ActiveRecord::Base model only
to
interact with the database and nothing else. My business logic is going
inside another models.
Sorry if i wasn’t clear enough before and thanks again for your time. =p
On Mon, Mar 25, 2013 at 2:51 PM, Paulo R. [email protected]
wrote:
with another patterns as well. And i want ActiveRecord::Base model only to
interact with the database and nothing else. My business logic is going
inside another models.Sorry if i wasn’t clear enough before and thanks again for your time. =p
If that’s the case, maybe you just want to work with the appropriate
data base gem/driver directly? (mysql2, sqlite3, postgres, etc)
Em tera-feira, 26 de maro de 2013 01h49min23s UTC-3, tamouse escreveu:
and the
simply not use features you don’t want?
Sorry if i wasn’t clear enough before and thanks again for your time. =p
If that’s the case, maybe you just want to work with the appropriate
data base gem/driver directly? (mysql2, sqlite3, postgres, etc)
Well, its an option. But i would like the code readbility of the
active_record methods and some good funcionalities like the finders. Im
still using rails on my projects, i just want to make sure that if
somebody
that is working on this project too, doesnt use callbacks and stuffs. I
want the models only to access the database.
On Sunday, 24 March 2013 12:59:00 UTC-4, Paulo R. wrote:
Thx for your reply. I want to make the models more light. I want to make
models what will only access the database (CRUD), without callbacks and the
other stuffs it loads.
Not to be rude, but this is still “what” you want to do.
Why are you trying to make the models “light”? Are you working in a
resource-constrained environment? Splitting off the callback system is
going to break plenty of stuff - for instance, :dependent => :destroy on
associations is implemented with a callback. Would it be sufficient to
simply not use features you don’t want?
–Matt J.
On Tue, Mar 26, 2013 at 9:15 AM, Paulo R. [email protected]
wrote:
Thx for your reply. I want to make the models more light. I want to
going
to
active_record methods and some good funcionalities like the finders. Im
still using rails on my projects, i just want to make sure that if somebody
that is working on this project too, doesnt use callbacks and stuffs. I want
the models only to access the database.
If you don’t use the callback and stuffs, do they actually get loaded?
I thought ActiveRecord only loaded the stuff that is getting used…
On Wed, Mar 27, 2013 at 3:26 AM, tamouse mailing lists
[email protected] wrote:
resource-constrained environment? Splitting off the callback system is
with another patterns as well. And i want ActiveRecord::Base model only
Well, its an option. But i would like the code readbility of the
active_record methods and some good funcionalities like the finders. Im
still using rails on my projects, i just want to make sure that if somebody
that is working on this project too, doesnt use callbacks and stuffs. I want
the models only to access the database.If you don’t use the callback and stuffs, do they actually get loaded?
I thought ActiveRecord only loaded the stuff that is getting used…
Also, hmm, wondering where you are on this project to actually see
that there is a practical need to worry about this at this point. Have
you seen performance benchmarks on your app already that show this is
now a problem? What I’ve found is that the stuff you seem to like, the
ORMish stuff and finders, actually ends up causing some serious
performance bottlenecks if you don’t think about how you gather data
in your application, and can generate some horrendous looking SQL.
Im not worried about performance. Im worried that i want to use it to
access the database only. All the other logics i want in a separate
class.
The callback logics i’m moving to a service. Some other logics to a
decorator and accessor.
I want to do this only to make sure that a person that does not know the
flow of developing can’t use it in a wrong way. I have a project with
this
idea on github, but right now i didnt push any decorator, accessor, or
model related logic. I have pushed only the work i made on controller to
use service.
But still, if u want to have a look at it, here it go:
Still, i just asked this here, because i thought that someone had tried
to
do it before. In case not, i will try by myself.
2013/3/27 tamouse mailing lists [email protected]
Em segunda-feira, 25 de maro de 2013 14h39min09s UTC-3, Matt J.
Not to be rude, but this is still “what” you want to do.
inside another models.
still using rails on my projects, i just want to make sure that if
you seen performance benchmarks on your app already that show this is
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
–
Em quarta-feira, 27 de maro de 2013 10h31min28s UTC-3, Hassan S.
escreveu:
Have you considered using an alternate ORM, e.g. DataMapper?
–
Hassan S. ------------------------ [email protected]<javascript:>
Hassan Schroeder | about.me
twitter: @hassan
Yes, i have considered it. But before i just want to know if is possible
to
do this using ActiveRecord. Is it possible to do or not?
On Wed, Mar 27, 2013 at 5:44 AM, Paulo H. Lopes Ribeiro
[email protected] wrote:
Still, i just asked this here, because i thought that someone had tried to
do it before. In case not, i will try by myself.
Uh, just checking – you know Rails has a flag to generate a new
app without ActiveRecord, yes?
Have you considered using an alternate ORM, e.g. DataMapper?
–
Hassan S. ------------------------ [email protected]
twitter: @hassan
Em quarta-feira, 27 de maro de 2013 11h36min19s UTC-3, Hassan S.
escreveu:
I think the real question is probably more like “Will the amount of
work required to remove or disable functionality from ActiveRecord
be worth it in the long run?” and only you can answer that.Good luck,
–
Hassan S. ------------------------ [email protected]<javascript:>
Hassan Schroeder | about.me
twitter: @hassan
Well, i would like to test it anyway. I think that if it could be done,
it
will worth. Im asking here exactly to not loose time on something that
can’t be done. =p
Anybody that have a more deep knowledge on this topic can answer me?
On Wed, Mar 27, 2013 at 7:04 AM, Paulo R. [email protected]
wrote:
Yes, i have considered it. But before i just want to know if is possible to
do this using ActiveRecord. Is it possible to do or not?
Dunno, never had a reason to try 
I think the real question is probably more like “Will the amount of
work required to remove or disable functionality from ActiveRecord
be worth it in the long run?” and only you can answer that.
Good luck,
–
Hassan S. ------------------------ [email protected]
twitter: @hassan
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs