brianthecoder / dm-is-schemaless Goto Github PK

I'm running the specs against mysql and after creating the schemaless_test database, the specs are throwing: "Column length too big for column 'body' (max = 21845); use BLOB or TEXT instead"

This occurs on every spec, here's an example trace:

8)
DataObjects::SQLError in 'DataMapper::Is::Schemaless structure has the property id'
Column length too big for column 'body' (max = 21845); use BLOB or TEXT instead
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:147:in `execute_non_query'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:147:in `create_model_storage'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/adapters/data_objects_adapter.rb:266:in `with_connection'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:144:in `create_model_storage'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:1166:in `create_model_storage'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:1260:in `auto_migrate_up!'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:49:in `send'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:49:in `repository_execute'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/model/descendant_set.rb:33:in `each'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/model/descendant_set.rb:33:in `each'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:48:in `repository_execute'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:42:in `auto_migrate_up!'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.1/lib/dm-core/migrations.rb:22:in `auto_migrate!'
./spec/integration/schemaless_spec.rb:10:

I'm guessing this is related to property :body, DataMapper::Types::Json, :default => {} but I don't know enough about DataMapper::Types::Json to know what if any changes need to be made.

I'm using the latest dm stuff (built from github) and I get the following error for the mysql on every test:

Incorrect table definition; there can be only one auto column and it must be defined as a key
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:140:in `execute_non_query'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:140:in `create_model_storage'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/adapters/data_objects_adapter.rb:283:in `with_connection'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:137:in `create_model_storage'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:1264:in `create_model_storage'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:1355:in `auto_migrate_up!'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:45:in `send'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/migrations.rb:45:in `repository_execute'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/model/descendant_set.rb:33:in `each'
/Library/Ruby/Gems/1.8/gems/dm-core-0.10.2/lib/dm-core/model/descendant_set.rb:33:in `

I don't have postgres installed, and the error does not occur on the sqlite in memory adapter. Any ideas what the issue might be?