> On Nov 16, 2014, at 4:49 PM, Michael Gentry <mgen...@masslight.net> wrote: > Perhaps I've missed the boat on this one
It depends. Most of the new API is very new and can be changed with no consequences. Some was already present in 3.2M1 a year ago (ObjectContext.select(..), Property). Still can change, but early adopters will be affected. > Replace "exp" with "where", I am ok with "where". We have complimentary methods in ObjectSelect: "and" and "or". Where..and...or mirrors SQL, which is probably a good thing. > "eq" with "is", I actually prefer "eq[uals]". Considering all other operations in the Property class, "is" creates a bit of asymmetry IMO. > "select" with "fetch" (since it is actually fetching your records), etc. I am open to it, though we'll need to review the API across the board. E.g. "select" / "selectOne" is already used in ObjectContext and originated from the new "Select" interface. I think "find*" is often used in other frameworks/languages, and sounds better than "select". We may refactor to use find/findFirst/findAll. > PS. Yesterday afternoon I was going through some of the JIRA issues > and saw some interesting screenshots for modeler changes where > attributes and relationships were being merged. Quite interested in > checking that out, too. Yep. That's committed to master. Andrus
