valid? raises error: wrong number of arguments (1 for 0)

dynamic tables

Hello all,

I've dabbled in datamapper in the past, but don't have much experience
in it.  I'm trying to evaluate its usefulness for solving a problem I
have.

I have a number of tables (probably ~50) that I need to get data
from.  Each table has 5 columns in common.  Beyond those 5 columns
each table has various numbers of various other columns; none of them
in common with other tables.

I would like to find a means of ORM that would allow me to declare a
single model that could handle the basic 5 pieces of common data, but
then also access the extra columns dynamically depending on what table
was specified.  I would really prefer NOT to have to write 50 or so
models (especially since this number is being added to and subtracted
from in an ongoing fashion).  I was wondering if perhaps Datamapper
might be able to solve this in a clean dynamic way.

Thoughts anyone?

Thanks,
Snowdall

--

-- 
You received this message because you are subscribed to the Google Groups "DataMapper" group.
To post to this group, send email to datamapper@...
To unsubscribe from this group, send email to datamapper+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.

What is the proper way to execute a SQL statement via DataMapper?

Listing all models in a repository (reflection)

Mutex already locked error in pooling.rb (jruby/torquebox)

DataObjects::Postgres::Result

Attributes on an Association

I need to store people, albums, photos, and the order that photos
appear in an album, so I decided to try adding a "position" attribute
to the association between Photo and Album. Consider the following
models:

class Person
  include DataMapper::Resource
...
end

class Album
  include DataMapper::Resource
...
  has n, :photos, "Photo", :through => :album_photos, :via => :photo
end

class Photo
  include DataMapper::Resource
...

  belongs_to :person, :required => true
  has n, :albums, "Album", :through => :album_photos, :via => :album
end

class AlbumPhoto
  include DataMapper::Resource

  property :position, Integer, :default => 1

  belongs_to :album, :key => true
  belongs_to :photo, :key => true

end

First, is such the right way to achieve this sort of thing? I didn't
see anything like this in the documentation.

To add a wrinkle, I have a model called Book which has a 1:M
relationship with Album. When I execute the following code

    album.album_photos.destroy
    album.album_photos << AlbumPhoto.new({:position =>3})
    book.update

I get "DataMapper::UpdateConflictError: Book#update cannot be called
on a dirty resource"

I am curious if my models are defined correctly. If so, how can I
delete all prior associations and update their positions "cleanly"?

Thanks.

--

-- 
You received this message because you are subscribed to the Google Groups "DataMapper" group.
To post to this group, send email to datamapper@...
To unsubscribe from this group, send email to datamapper+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.

Query Order

Guys,
how can I set the query (all, first, etc) order to something like
"ifnull(column1, column2) asc", I just can "order =>
[:column1.asc, :column2.asc]", but it does't work for null columns.
Thanks

--

-- 
You received this message because you are subscribed to the Google Groups "DataMapper" group.
To post to this group, send email to datamapper@...
To unsubscribe from this group, send email to datamapper+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.

Many to one association question

decimal field using sqlite

hi, I am having some problem here with field Decimal

My Class:

require 'dm-core'

class Registry
  include DataMapper::Resource

  property :num, Decimal, :key => true,  :precision => 20, :scale => 0
end

require 'dm-migrations'
DataMapper.finalize
DataMapper.setup(:default, 'sqlite::memory:')
DataMapper.auto_migrate!

My Test:

// I start irb
$ irb -r ./dm
/home/arthur/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/yaml.rb:56:in
`<top (required)>':
It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your
ruby.

// and create a new registry
ruby-1.9.3-p0 :001 > r = Registry.new(:num => 321512420108210029)
 => #<Registry @num=#<BigDecimal:9771c54,'0.3215124201 08210029E18',
18(27)>>  // bigdecimal is showing correct num
ruby-1.9.3-p0 :002 > r.save
 => true
ruby-1.9.3-p0 :003 > Registry.all
 => [#<Registry @num=#<BigDecimal:98358e8,'0.3215124201 08210048E18',
18(27)>>] // num is wrong
ruby-1.9.3-p0 :004 >
Registry.all.first.num.to_i                                                             //
trying to convert to int
 =>
321512420108210048                                                                                          //
wrong value
ruby-1.9.3-p0 :005 >
BigDecimal.new(321512420108210029).to_i                                //
here, aparently bigdecimal is working correct
 => 321512420108210029

Anyone can help me ? What am I doing wrong ?
I try too on mysql, and I have the same problem.

Thanks

--

-- 
You received this message because you are subscribed to the Google Groups "DataMapper" group.
To post to this group, send email to datamapper@...
To unsubscribe from this group, send email to datamapper+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.

Call to DataMapper.auto_upgrade! doesn't return