Adding ability to use getters and setters as opposed to public methods.

[iainconnor]

Great work on this library. I was always a fan of the syntax in https://github.com/pardom/ActiveAndroid, but the performance hit against reflection on annotations seemed like a downside so I was really happy to see Ollie pop up.

One of the things I didn't particularly like when integrating with my existing model schema was that all the fields had to be public, so I added a new annotation called @GetSet that tells the generated classes to look for getter and setter methods instead of accessing the fields directly.

[iainconnor]

Nice idea.

Part of the reason for my original syntax was a thought in the back of my head on whether you should consider making the @Column annotation's parameter optional, and automatically generate it based on the field name, since you know those are unique and meaningful. But thinking a bit more on that, you'd probably want them as known quantities so you can use those final variables for writing queries as well;

new Select().from(Post.class).where(Post.TITLE + "=?", "Foobar");

as opposed to

new Select().from(Post.class).where("title=?", "Foobar");

[pardom-zz]

Part of the reason for my original syntax was a thought in the back of my head on whether you should consider making the @column annotation's parameter optional, and automatically generate it based on the field name, since you know those are unique and meaningful.

Yes, that's what I've been wrestling with. However, with your approach we rely on the user keeping the method names up-to-date since methods can't be statically linked to the method name string, which adds another step to refactoring method names.

Another thing I prefer about my syntax is that it enforces the idea that Ollie is processing and referencing those methods. There is no magic happening.

Again, I haven't settled on one particular idea and I'm open to improvements on mine. It doesn't have to be @Column annotations either. It could be @Get(TITLE) and @Set(TITLE) (although we can infer get and set by the return type so something like @Accessor(TITLE) could be better).

[iainconnor]

Yup, I see what you mean. The way you suggested does keep it nice and clear, and keeps Ollie (and, really, the database) at a nice distance from the models themselves.

Updated to see what it feels like with @Accessor(TITLE) in the mix.

Even though we can infer the get and set, I still might consider making @Accessor and @Mutator separate annotations, just to be consistent with what those terms actually mean.

[pardom-zz]

After some thought, I think the correct way to handle this is by convention. If you have a private @Column fooBar field, there should be associated getFooBar and setFooBar fields.