Listado de todos los modelos de mi aplica ciÃ³n Rails

fearx · September 23, 2008, 6:45pm

Hola gente,

Busco la manera en que se pueda listar (en forma de Array o lo que
sea) todos los ActiveRecord (o sus nombres en String) de mi
aplicaciónRails.

Busco esto para poder hacer un:
Modelo1.delete(:all)
Modelo2.delete(:all)
Modelo3.delete(:all)

Si por lo menos tengo los nombres igual con reflection puedo hacerlo.

He llegado hasta
aquí:
?> sql = ActiveRecord::Base.connection()

result = sql.execute “select table_name from information_schema.Tables where table_schema = ‘confror’”
result.each {|r| puts r[0]}
tabla1
tabla2
tabla3

Podría con esto intentar hacer ‘capitalize’ o algo… pero pregunto
primero en vez de empezar a liarme por donde no es.

Cualquier sugerencia es bienvenida.

Saludos
f.

fearx · September 23, 2008, 7:01pm

Fernando,

te sirve un Dir.glob("#{RAILS_ROOT}/app/models/*.rb") ?
Te devuelve un array con los nombres de los ficheros que tienes en app/
models, luego los puedes tratar del estilo:

Dir.glob("#{RAILS_ROOT}/app/models/*.rb").each {|file| file.gsub(/.rb
$/,’’).constantize.delete_all }

Aprox…

Salutaciones,

Isaac Feliu

fearx · September 23, 2008, 7:25pm

On Tue, Sep 23, 2008 at 7:00 PM, Isaac Feliu PÃ©rez
[email protected] wrote:

Dir.glob(“#{RAILS_ROOT}/app/models/*.rb”).each {|file| file.gsub(/.rb
$/,‘’).constantize.delete_all }

Y si los modelos no son ActiveRecord?

fearx · September 23, 2008, 7:29pm

2008/9/23 Francesc E. [email protected]:

On Tue, Sep 23, 2008 at 7:00 PM, Isaac Feliu Pérez
[email protected] wrote:

Dir.glob(“#{RAILS_ROOT}/app/models/*.rb”).each {|file| file.gsub(/.rb
$/,‘’).constantize.delete_all }

Y si los modelos no son ActiveRecord?

Son ActiveRecord … :)… por no buscar una solución demasiado generalista.

fearx · September 23, 2008, 7:39pm

Dir[“#{RAILS_ROOT}/app/models/**/*.rb”].each do |m|
class_name = m.sub(/.rb$/,‘’).camelize
klass = class_name.split(‘::’).inject(Object){ |klass,part|
klass.const_get(part) }
self.delete_all if klass < ActiveRecord::Base &&
!klass.abstract_class?
end

Lo dejo en un Gist 12343’s gists · GitHub

On Tue, Sep 23, 2008 at 7:05 PM, Fernando G.

fearx · September 23, 2008, 7:41pm

2008/9/23 Isaac Feliu Pérez [email protected]:

Fernando,

te sirve un Dir.glob(“#{RAILS_ROOT}/app/models/*.rb”) ?
Te devuelve un array con los nombres de los ficheros que tienes en app/
models, luego los puedes tratar del estilo:

Dir.glob(“#{RAILS_ROOT}/app/models/*.rb”).each {|file| file.gsub(/.rb
$/,‘’).constantize.delete_all }

Buena aproximación

f.

fearx · September 23, 2008, 7:25pm

Hola,

Busco la manera en que se pueda listar (en forma de Array o lo que
sea) todos los ActiveRecord (o sus nombres en String) de mi aplicación
Rails.

Yo tengo esto en un proyecto donde necesito precargar los modelos porque
los guardo en memcached y si no al deserializar me puede dar problemas

ActiveRecord::Base.connection.tables.each do |model|
begin
“#{model.classify}”.constantize
rescue Exception
nil
end
end

Sólo te funcionará en el caso de que tus modelos sigan las convenciones
de nomenclatura. Además, si tienes varios modelos hijos que extiendan de
un mismo modelo padre y compartan esa tabla, los hijos tampoco te los
cargará. Como entiendo que no tienes ninguno de los dos, con eso te
debería servir.

En caso de que tuvieses modelos con nomenclatura no estándar, podrías
hacer un ls de los ficheros dentro de app/models y convertir los nombres
de ficheros a constantes. El problema de ese enfoque es que los modelos
que vengan de plugins, o que estén en subcarpetas, no te los
reconocerá.
suerte,

j

–
javier ramírez

…i do ruby on rails development in madrid, spain, at
http://www.aspgems.com
…you can find out more about me on http://formatinternet.wordpress.com
and http://workingwithrails.com/person/5987-javier-ramirez

fearx · September 23, 2008, 7:45pm

2008/9/23 Francesc E. [email protected]:

Dir[“#{RAILS_ROOT}/app/models/**/*.rb”].each do |m|
class_name = m.sub(/.rb$/,‘’).camelize
klass = class_name.split(‘::’).inject(Object){ |klass,part|
klass.const_get(part) }
self.delete_all if klass < ActiveRecord::Base && !klass.abstract_class?
end

Madre mía la que has montado aquí

Lo dejo en un Gist 12343’s gists · GitHub

Mola esto de gist… no lo conocía.

f.

fearx · September 23, 2008, 7:41pm

El día 23 de septiembre de 2008 19:03, javier ramirez
[email protected]
escribió:> begin

 "#{model.classify}".constantize
 rescue Exception
   nil
 end

end

funciona

fearx · September 23, 2008, 7:48pm

On Tue, Sep 23, 2008 at 7:15 PM, Fernando G.
[email protected] wrote:

Madre mÃa la que has montado aquÃ

Tu no querias los modelos? Quizas es una paja mental, pero es la
manera de saber que modelos son AR.

He actualizado el Gist 12343’s gists · GitHub

fearx · September 23, 2008, 7:56pm

No es culpa de ni de 1.2.3 ni de 2.0.1 ni de nada relacionado con
Ruby. Me he colado.

Ahora si … 12343’s gists · GitHub

fearx · September 23, 2008, 7:49pm

2008/9/23 Francesc E. [email protected]:

Dir[“#{RAILS_ROOT}/app/models/**/*.rb”].each do |m|
class_name = m.sub(/.rb$/,‘’).camelize
klass = class_name.split(‘::’).inject(Object){ |klass,part|
klass.const_get(part) }
self.delete_all if klass < ActiveRecord::Base && !klass.abstract_class?
end

Me da este error en RAILS 1.2.3:

NameError: uninitialized constant Script

?> Dir[“#{RAILS_ROOT}/app/models/**/*.rb”].each do |m|
?> class_name = m.sub(/.rb$/,‘’).camelize

klass = class_name.split(‘::’).inject(Object){ |klass,part| klass.const_get(part) }
self.find(:all) if klass < ActiveRecord::Base && !klass.abstract_class?
end
NameError: uninitialized constant Script
from
./script/…/config/…/config/…/vendor/rails/activerecord/lib/…/…/activesupport/lib/active_support/dependencies.rb:266:in
load_missing_constant' from ./script/../config/../config/../vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:452:in const_missing’
from
./script/…/config/…/config/…/vendor/rails/activerecord/lib/…/…/activesupport/lib/active_support/dependencies.rb:464:in
const_missing' from (irb):69:in const_get’
from (irb):69
from (irb):71:in inject' from (irb):69:in each’
from (irb):69:in inject' from (irb):69 from (irb):67:in each’
from (irb):67

Y este en Rails 2.0.1 Aunque igual no es cosa de la versión sino de
los modelos de cada proyecto:

?> Dir[“#{RAILS_ROOT}/app/models/**/*.rb”].each do |m|
?> class_name = m.sub(/.rb$/,‘’).camelize

klass = class_name.split(‘::’).inject(Object){ |klass,part| klass.const_get(part) }
self.find(:all) if klass < ActiveRecord::Base && !klass.abstract_class?
end
ArgumentError: interning empty string
from (irb):9:in const_get' from (irb):9 from (irb):11:in inject’
from (irb):9:in each' from (irb):9:in inject’
from (irb):9
from (irb):7:in `each’
from (irb):7
from :0

En cualquier caso no te vuelvas loco… la solución de javier ramirez
me parece limpia y funa bien.

Gracias.
f.

fearx · September 24, 2008, 12:10am

El día 23 de septiembre de 2008 23:30, Guillermo
[email protected]
escribió:> AR guarda la clase cada vez que se hereda de de AR::Base como puedes ver

aquí.
http://github.com/rails/rails/tree/master/activerecord/lib/active_record/base.rb#L397
Sin tener mucha idea, podrías usar ese @@subclases.

Masié para
mí:>> ActiveRecord::Base@@subclases
NameError: uninitialized class variable @@subclases in Object
from (irb):3

ActiveRecord::Base.send(“@@subclases”)
NoMethodError: undefined method @@subclases' for ActiveRecord::Base:Class from ./script/../config/../config/../vendor/rails/activerecord/lib/active_record/base.rb:1235:in method_missing’
from (irb):4:in `send’
from (irb):4

Sin embargo, no te es más fácil borrar todas las tablas

Quería borrarlas usando ActiveRecord

, y hacer un
rake:db:schema:load

Esta es buena también gracias.

Graaacias… te debo un fortuna

f.

fearx · September 24, 2008, 12:24am

On 23 Sep 2008, at 23:40, Fernando G. wrote:

Masié para mí:

ActiveRecord::Base@@subclases
NameError: uninitialized class variable @@subclases in Object
from (irb):3

ActiveRecord::Base.send("@@subclases")

ActiveRecord::Base.send(:subclasses)

Pero eso solo te va a dar los modelos que ya estan cargados (AR usa
lazy loading…)

Quería borrarlas usando ActiveRecord

ActiveRecord::Base.connection.tables

…te da la lista de tablas.

De aqui se puede ir borrando.

-christos

fearx · September 24, 2008, 12:38am

Genial… gracias por la catarata de ideas.

Saludos
f.

fearx · September 23, 2008, 11:31pm

AR guarda la clase cada vez que se hereda de de AR::Base como puedes ver
aquÃ.

github.com

rails/rails/blob/main/activerecord/lib/active_record/base.rb#L397


      
          # frozen_string_literal: true
          
          
require "active_support/benchmarkable"
          require "active_support/dependencies"
          require "active_support/descendants_tracker"
          require "active_support/time"
          require "active_support/core_ext/class/subclasses"
          require "active_record/log_subscriber"
          require "active_record/explain_subscriber"
          require "active_record/relation/delegation"
          require "active_record/attributes"
          require "active_record/type_caster"
          require "active_record/database_configurations"
          
          
module ActiveRecord # :nodoc:
            # = Active Record
            #
            # Active Record objects don't specify their attributes directly, but rather infer them from
            # the table definition with which they're linked. Adding, removing, and changing attributes
            # and their type is done directly in the database. Any change is instantly reflected in the
            # Active Record objects. The mapping that binds a given Active Record class to a certain
            # database table will happen automatically in most common cases, but can be overwritten for the uncommon ones.
            #
            # See the mapping rules in table_name and the full example in link:files/activerecord/README_rdoc.html for more insight.
            #
            # == Creation
            #
            # Active Records accept constructor parameters either in a hash or as a block. The hash
            # method is especially useful when you're receiving the data from somewhere else, like an
            # HTTP request. It works like this:
            #
            #   user = User.new(name: "David", occupation: "Code Artist")
            #   user.name # => "David"
            #
            # You can also use block initialization:
            #
            #   user = User.new do |u|
            #     u.name = "David"
            #     u.occupation = "Code Artist"
            #   end
            #
            # And of course you can just create a bare object and specify the attributes after the fact:
            #
            #   user = User.new
            #   user.name = "David"
            #   user.occupation = "Code Artist"
            #
            # == Conditions
            #
            # Conditions can either be specified as a string, array, or hash representing the WHERE-part of an SQL statement.
            # The array form is to be used when the condition input is tainted and requires sanitization. The string form can
            # be used for statements that don't involve tainted data. The hash form works much like the array form, except
            # only equality and range is possible. Examples:
            #
            #   class User < ActiveRecord::Base
            #     def self.authenticate_unsafely(user_name, password)
            #       where("user_name = '#{user_name}' AND password = '#{password}'").first
            #     end
            #
            #     def self.authenticate_safely(user_name, password)
            #       where("user_name = ? AND password = ?", user_name, password).first
            #     end
            #
            #     def self.authenticate_safely_simply(user_name, password)
            #       where(user_name: user_name, password: password).first
            #     end
            #   end
            #
            # The <tt>authenticate_unsafely</tt> method inserts the parameters directly into the query
            # and is thus susceptible to SQL-injection attacks if the <tt>user_name</tt> and +password+
            # parameters come directly from an HTTP request. The <tt>authenticate_safely</tt> and
            # <tt>authenticate_safely_simply</tt> both will sanitize the <tt>user_name</tt> and +password+
            # before inserting them in the query, which will ensure that an attacker can't escape the
            # query and fake the login (or worse).
            #
            # When using multiple parameters in the conditions, it can easily become hard to read exactly
            # what the fourth or fifth question mark is supposed to represent. In those cases, you can
            # resort to named bind variables instead. That's done by replacing the question marks with
            # symbols and supplying a hash with values for the matching symbol keys:
            #
            #   Company.where(
            #     "id = :id AND name = :name AND division = :division AND created_at > :accounting_date",
            #     { id: 3, name: "37signals", division: "First", accounting_date: '2005-01-01' }
            #   ).first
            #
            # Similarly, a simple hash without a statement will generate conditions based on equality with the SQL AND
            # operator. For instance:
            #
            #   Student.where(first_name: "Harvey", status: 1)
            #   Student.where(params[:student])
            #
            # A range may be used in the hash to use the SQL BETWEEN operator:
            #
            #   Student.where(grade: 9..12)
            #
            # An array may be used in the hash to use the SQL IN operator:
            #
            #   Student.where(grade: [9,11,12])
            #
            # When joining tables, nested hashes or keys written in the form 'table_name.column_name'
            # can be used to qualify the table name of a particular condition. For instance:
            #
            #   Student.joins(:schools).where(schools: { category: 'public' })
            #   Student.joins(:schools).where('schools.category' => 'public' )
            #
            # == Overwriting default accessors
            #
            # All column values are automatically available through basic accessors on the Active Record
            # object, but sometimes you want to specialize this behavior. This can be done by overwriting
            # the default accessors (using the same name as the attribute) and calling
            # +super+ to actually change things.
            #
            #   class Song < ActiveRecord::Base
            #     # Uses an integer of seconds to hold the length of the song
            #
            #     def length=(minutes)
            #       super(minutes.to_i * 60)
            #     end
            #
            #     def length
            #       super / 60
            #     end
            #   end
            #
            # == Attribute query methods
            #
            # In addition to the basic accessors, query methods are also automatically available on the Active Record object.
            # Query methods allow you to test whether an attribute value is present.
            # Additionally, when dealing with numeric values, a query method will return false if the value is zero.
            #
            # For example, an Active Record User with the <tt>name</tt> attribute has a <tt>name?</tt> method that you can call
            # to determine whether the user has a name:
            #
            #   user = User.new(name: "David")
            #   user.name? # => true
            #
            #   anonymous = User.new(name: "")
            #   anonymous.name? # => false
            #
            # Query methods will also respect any overrides of default accessors:
            #
            #   class User
            #     # Has admin boolean column
            #     def admin
            #       false
            #     end
            #   end
            #
            #   user.update(admin: true)
            #
            #   user.read_attribute(:admin)  # => true, gets the column value
            #   user[:admin] # => true, also gets the column value
            #
            #   user.admin   # => false, due to the getter override
            #   user.admin?  # => false, due to the getter override
            #
            # == Accessing attributes before they have been typecasted
            #
            # Sometimes you want to be able to read the raw attribute data without having the column-determined
            # typecast run its course first. That can be done by using the <tt><attribute>_before_type_cast</tt>
            # accessors that all attributes have. For example, if your Account model has a <tt>balance</tt> attribute,
            # you can call <tt>account.balance_before_type_cast</tt> or <tt>account.id_before_type_cast</tt>.
            #
            # This is especially useful in validation situations where the user might supply a string for an
            # integer field and you want to display the original string back in an error message. Accessing the
            # attribute normally would typecast the string to 0, which isn't what you want.
            #
            # == Dynamic attribute-based finders
            #
            # Dynamic attribute-based finders are a mildly deprecated way of getting (and/or creating) objects
            # by simple queries without turning to SQL. They work by appending the name of an attribute
            # to <tt>find_by_</tt> like <tt>Person.find_by_user_name</tt>.
            # Instead of writing <tt>Person.find_by(user_name: user_name)</tt>, you can use
            # <tt>Person.find_by_user_name(user_name)</tt>.
            #
            # It's possible to add an exclamation point (!) on the end of the dynamic finders to get them to raise an
            # ActiveRecord::RecordNotFound error if they do not return any records,
            # like <tt>Person.find_by_last_name!</tt>.
            #
            # It's also possible to use multiple attributes in the same <tt>find_by_</tt> by separating them with
            # "_and_".
            #
            #  Person.find_by(user_name: user_name, password: password)
            #  Person.find_by_user_name_and_password(user_name, password) # with dynamic finder
            #
            # It's even possible to call these dynamic finder methods on relations and named scopes.
            #
            #   Payment.order("created_on").find_by_amount(50)
            #
            # == Saving arrays, hashes, and other non-mappable objects in text columns
            #
            # Active Record can serialize any object in text columns using YAML. To do so, you must
            # specify this with a call to the class method
            # {serialize}[rdoc-ref:AttributeMethods::Serialization::ClassMethods#serialize].
            # This makes it possible to store arrays, hashes, and other non-mappable objects without doing
            # any additional work.
            #
            #   class User < ActiveRecord::Base
            #     serialize :preferences
            #   end
            #
            #   user = User.create(preferences: { "background" => "black", "display" => large })
            #   User.find(user.id).preferences # => { "background" => "black", "display" => large }
            #
            # You can also specify a class option as the second parameter that'll raise an exception
            # if a serialized object is retrieved as a descendant of a class not in the hierarchy.
            #
            #   class User < ActiveRecord::Base
            #     serialize :preferences, Hash
            #   end
            #
            #   user = User.create(preferences: %w( one two three ))
            #   User.find(user.id).preferences    # raises SerializationTypeMismatch
            #
            # When you specify a class option, the default value for that attribute will be a new
            # instance of that class.
            #
            #   class User < ActiveRecord::Base
            #     serialize :preferences, OpenStruct
            #   end
            #
            #   user = User.new
            #   user.preferences.theme_color = "red"
            #
            #
            # == Single table inheritance
            #
            # Active Record allows inheritance by storing the name of the class in a
            # column that is named "type" by default. See ActiveRecord::Inheritance for
            # more details.
            #
            # == Connection to multiple databases in different models
            #
            # Connections are usually created through
            # {ActiveRecord::Base.establish_connection}[rdoc-ref:ConnectionHandling#establish_connection] and retrieved
            # by ActiveRecord::Base.connection. All classes inheriting from ActiveRecord::Base will use this
            # connection. But you can also set a class-specific connection. For example, if Course is an
            # ActiveRecord::Base, but resides in a different database, you can just say <tt>Course.establish_connection</tt>
            # and Course and all of its subclasses will use this connection instead.
            #
            # This feature is implemented by keeping a connection pool in ActiveRecord::Base that is
            # a hash indexed by the class. If a connection is requested, the
            # {ActiveRecord::Base.retrieve_connection}[rdoc-ref:ConnectionHandling#retrieve_connection] method
            # will go up the class-hierarchy until a connection is found in the connection pool.
            #
            # == Exceptions
            #
            # * ActiveRecordError - Generic error class and superclass of all other errors raised by Active Record.
            # * AdapterNotSpecified - The configuration hash used in
            #   {ActiveRecord::Base.establish_connection}[rdoc-ref:ConnectionHandling#establish_connection]
            #   didn't include an <tt>:adapter</tt> key.
            # * AdapterNotFound - The <tt>:adapter</tt> key used in
            #   {ActiveRecord::Base.establish_connection}[rdoc-ref:ConnectionHandling#establish_connection]
            #   specified a non-existent adapter
            #   (or a bad spelling of an existing one).
            # * AssociationTypeMismatch - The object assigned to the association wasn't of the type
            #   specified in the association definition.
            # * AttributeAssignmentError - An error occurred while doing a mass assignment through the
            #   {ActiveRecord::Base#attributes=}[rdoc-ref:AttributeAssignment#attributes=] method.
            #   You can inspect the +attribute+ property of the exception object to determine which attribute
            #   triggered the error.
            # * ConnectionNotEstablished - No connection has been established.
            #   Use {ActiveRecord::Base.establish_connection}[rdoc-ref:ConnectionHandling#establish_connection] before querying.
            # * MultiparameterAssignmentErrors - Collection of errors that occurred during a mass assignment using the
            #   {ActiveRecord::Base#attributes=}[rdoc-ref:AttributeAssignment#attributes=] method.
            #   The +errors+ property of this exception contains an array of
            #   AttributeAssignmentError
            #   objects that should be inspected to determine which attributes triggered the errors.
            # * RecordInvalid - raised by {ActiveRecord::Base#save!}[rdoc-ref:Persistence#save!] and
            #   {ActiveRecord::Base.create!}[rdoc-ref:Persistence::ClassMethods#create!]
            #   when the record is invalid.
            # * RecordNotFound - No record responded to the {ActiveRecord::Base.find}[rdoc-ref:FinderMethods#find] method.
            #   Either the row with the given ID doesn't exist or the row didn't meet the additional restrictions.
            #   Some {ActiveRecord::Base.find}[rdoc-ref:FinderMethods#find] calls do not raise this exception to signal
            #   nothing was found, please check its documentation for further details.
            # * SerializationTypeMismatch - The serialized object wasn't of the class specified as the second parameter.
            # * StatementInvalid - The database server rejected the SQL statement. The precise error is added in the message.
            #
            # *Note*: The attributes listed are class-level attributes (accessible from both the class and instance level).
            # So it's possible to assign a logger to the class through <tt>Base.logger=</tt> which will then be used by all
            # instances in the current object space.
            class Base
              extend ActiveModel::Naming
          
          
    extend ActiveSupport::Benchmarkable
              extend ActiveSupport::DescendantsTracker
          
          
    extend ConnectionHandling
              extend QueryCache::ClassMethods
              extend Querying
              extend Translation
              extend DynamicMatchers
              extend DelegatedType
              extend Explain
              extend Enum
              extend Delegation::DelegateCache
              extend Aggregations::ClassMethods
          
          
    include Core
              include Persistence
              include ReadonlyAttributes
              include ModelSchema
              include Inheritance
              include Scoping
              include Sanitization
              include AttributeAssignment
              include ActiveModel::Conversion
              include Integration
              include Validations
              include CounterCache
              include Attributes
              include Locking::Optimistic
              include Locking::Pessimistic
              include Encryption::EncryptableRecord
              include AttributeMethods
              include Callbacks
              include Timestamp
              include Associations
              include SecurePassword
              include AutosaveAssociation
              include NestedAttributes
              include Transactions
              include TouchLater
              include NoTouching
              include Reflection
              include Serialization
              include Store
              include SecureToken
              include TokenFor
              include SignedId
              include Suppressor
              include Normalization
              include Marshalling::Methods
            end
          
          
  ActiveSupport.run_load_hooks(:active_record, Base)
          end

This file has been truncated. show original

Sin tener mucha idea, podrÃas usar ese @@subclases.

Sin embargo, no te es mÃ¡s fÃ¡cil borrar todas las tablas, y hacer un
rake:db:schema:load