-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support embedded objects #9
Comments
Hola, de ante mano agradecer el gran trabajo que estás haciendo, en la librería room de Android siempre tuve un descontento y es que no se pudiera colocar usar variables solo para cargar dato de la consulta, ya que se debía colocar como un campo para que en la consulta lo tomará, esto es para el caso un join con otra tabla, no en todos los casos es necesario todo el objeto de otra clase, sería bueno que se agregara una opción al columnInfo que permita usar la variable para solo consulta. |
Hi @willgsoft! I'm happy to see your interest in the library and would like to help. Unluckily, my Spanish skills are mediocre and Google Translate didn't help this time. I think it would be beneficial for me and others to keep the conversation in English. |
I've just run into an issue which I think relates to this. I have a "Day" entity, each of which has several "Temp" fields. The "Temp" object is a custom object which has 2 fields of its own - a double and a bool. I wrote a Type Converter so Floor will manage the Temp objects, but when I call an update method for a Day, the bool field of the Temp is not getting updated in the database. My theory is that the database does not recognize the change, as the Day still has the same Temp object - it doesn't "see" the change to the Temp object's property. I could be wrong though, I'm not sure I completely understand how Floor and Sql work. Any help would be appreciated. |
An entity should be able to hold nested objects. There are different strategies for the implementation of this. One is, to embed all fields of the nested object in the surrounding object table.
The text was updated successfully, but these errors were encountered: