We need to take a look into usage of ´refenreces_one´ / ´referenecs_many´. Maybe when you do a references_one it should create the accessor methods for the referenced id(?) ..but we don't do that in the context of a table. Then we normally have to say :store_in => 'some_column_family' to get it to auto-define the accessor methods, or else the responsible for defining the foreign key method is put on the developer.
In an embedded context however, there are no different :store_in option to be given - and what happens if we give it the store_in option in a context of embedded classes? We need to investigate this future ;)
We need to take a look into usage of ´refenreces_one´ / ´referenecs_many´. Maybe when you do a references_one it should create the accessor methods for the referenced id(?) ..but we don't do that in the context of a table. Then we normally have to say :store_in => 'some_column_family' to get it to auto-define the accessor methods, or else the responsible for defining the foreign key method is put on the developer.
In an embedded context however, there are no different :store_in option to be given - and what happens if we give it the store_in option in a context of embedded classes? We need to investigate this future ;)