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

Change Record.getValue() and setValue() to get() and set() #2211

Closed
lukaseder opened this Issue Feb 16, 2013 · 2 comments

Comments

Projects
None yet
1 participant
@lukaseder
Member

lukaseder commented Feb 16, 2013

jOOQ's API would be much more lean, if these method name replacements were made:

  • Record.getValue() -> Record.get()
  • Record.setValue() -> Record.set()

This would add a lot of value to the Kotlin integration, in case of which the following syntax sugar would be applicable:

record[TABLE.FIELD] = value; // set
value = record[TABLE.FIELD]; // get

See #2115 for a comprehensive list of methods whose name should be changed by jOOQ 4.0

@lukaseder

This comment has been minimized.

Show comment
Hide comment
@lukaseder

lukaseder Mar 15, 2015

Member

jOOQ has gotten too much traction now - we shouldn't implement such cosmetic, yet backwards-incompatible changes. Users won't like that

Member

lukaseder commented Mar 15, 2015

jOOQ has gotten too much traction now - we shouldn't implement such cosmetic, yet backwards-incompatible changes. Users won't like that

@lukaseder

This comment has been minimized.

Show comment
Hide comment
@lukaseder

lukaseder Feb 21, 2016

Member

In order not to annoy existing jOOQ users, the old methods won't be deprecated yet (although a warning remark is added to the Javadoc).

We can still decide in jOOQ 4.0, if getValue() and setValue() should be removed.

Member

lukaseder commented Feb 21, 2016

In order not to annoy existing jOOQ users, the old methods won't be deprecated yet (although a warning remark is added to the Javadoc).

We can still decide in jOOQ 4.0, if getValue() and setValue() should be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment