SUGAR reformats entity properties about sugar HOT 7 CLOSED

The intent is to have a consistent column naming convention.. But, on second thought, not a bad idea to just use the property names as it is..

from sugar.

Any time scale for the change?

from sugar.

I'd take some time to change this.. I'm considering options like making this configuration with annotations or any particular interface. That's because some apps may want to have a different column name than the property name.

However, for you, you could just change the
https://github.com/satyan/sugar/blob/master/library/src/com/orm/StringUtil.java

Remove the property renaming logic and you'd get the same property names as the column names.
Let me know if this helps.

from sugar.

Satyan,

I'm having a similar problem. My model is:
public class Region extends SugarRecord {

private String externalId;
private String name;
    ...

}

And the externalId was created as "external_id" column. So, when I build a query, I have to send the prop as the name of the column instead of the name of the property. Example:
List list = Select.from(Region.class)
.where(Condition.prop("external_id").eq("abc123"))
.list();

Could you call the StringUtil.toSQLName when we add a property to a condition?

The code would be like this:
public Condition(String property) {
this.property = StringUtil.toSQLName(property);
}

I think it will solve the problem.

Thanks!!

from sugar.

Hmm.. that's a nice suggestion. I'm considering Annotations for custom property names as well. Thanks, I'll look at this option too.

from sugar.

The right approach is probably to beef up the query builder modules, with a specific interface for userland names that'll automatically do the name conversions under the hood.

from sugar.

now we have @column annotation that enable us to use any name for a specific column

from sugar.