Skip to content
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

Settings.backslashEscaping is not applied to LIKE .. ESCAPE clause - Merge [#5150] #5151

Closed
lukaseder opened this issue Mar 15, 2016 · 0 comments

Comments

@lukaseder
Copy link
Member

No description provided.

@lukaseder lukaseder added this to the Version 3.7.4 milestone Mar 15, 2016
lukaseder added a commit that referenced this issue May 6, 2016
================================================================================

This is a patch release with some useful fixes for the 3.7 branch

Breaking changes
----------------
#5234 - Remove DSL.field(Row[N]) to speed up client side compilation time

Bug Fixes
---------
#5129 - Don't generate javax.validation.NotNull for defaulted columns
#5135 - OracleConnection Class not found when jOOQ runs in OSGi and ARRAY types are bound
#5141 - DSL.currentTimestamp() cannot be used as a default value for a column, via alterTable
#5147 - Type handling issue when using a custom type with a Postgres UDT field
#5151 - Settings.backslashEscaping is not applied to LIKE .. ESCAPE clause
#5159 - FILTER (WHERE ...) and OVER() is not applied to PostgreSQL ARRAY_AGG()
#5168 - Possible NPE when calling InsertImpl.set(Field, Select) with a null Select
#5175 - NullPointerException when calling Query.getSQL() on an unattached Query
#5183 - Meta Table.getKeys() returns an empty list containing "null", if a table has no primary key
#5187 - Excessive log level when ignoring foreign key referencing an out-of-scope schema
#5188 - DefaultBindings for OffsetTime and OffsetDateTime handle negative offsets
#5194 - PostgreSQL timestamp deserialisation loses millisecond precision, when timestamp is contained in an array of composite types
#5203 - MySQL unsigned data types in stored procedures and functions are not captured correctly by jOOQ's code generator
#5220 - SQLFeatureNotSupportedException thrown in some (unsupported) SQLDialects when initalizing MetaDataFieldProvider
#5226 - Results.clear() does not remove update counts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant