Re: Object freeze and data reading

2017-01-16 21:40 GMT+01:00 Jeremy Evans > Thanks. This does appear to be a bug, caused because the associations > hash was frozen before validation (freeze validates), when it probably > shouldn't be frozen until after. > .../... > You could work

Re: Migrations with sharded databases question

On Monday, January 16, 2017 at 7:37:49 AM UTC-8, Jay Danielian wrote: > > I've been able to successfuly setup my sharded databases and load records > into it with my custom sharding scheme. So far I run > Sequel::Migrator.apply(DB, './migrate') and it picks up my migration > scripts. In my

Re: Object freeze and data reading

On Monday, January 16, 2017 at 2:10:31 AM UTC-8, David Espada wrote: > > 2017-01-13 16:22 GMT+01:00 Jeremy Evans: > >> Are you running the current version of Sequel? I remember fixing an >> issue like this sometime in the past. The line number you give doesn't >> really make sense to cause the

Migrations with sharded databases question

I've been able to successfuly setup my sharded databases and load records into it with my custom sharding scheme. So far I run Sequel::Migrator.apply(DB, './migrate') and it picks up my migration scripts. In my migration script I am doing this: Sequel.migration do up do DB.each_server

Re: Object freeze and data reading

2017-01-13 16:22 GMT+01:00 Jeremy Evans : > Are you running the current version of Sequel? I remember fixing an issue > like this sometime in the past. The line number you give doesn't really > make sense to cause the issue in the current code. If you are running the >