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
Add property url on (relevant) data sources [JDBC521] #217
Comments
Modified by: @mrotteveelFix Version: Jaybird 2.2.15 [ 10860 ] Fix Version: Jaybird 3.0.4 [ 10861 ] Fix Version: Jaybird 4 [ 10441 ] description: Add a property url (or maybe jdbcUrl) on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration. See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for a use case. This may need to wait until the connection property / dpb handling has been revised. => Add a property url on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration. For some reason this property seems to be required to exist by either Spring JPA or Hibernate. See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for an example. For now tentatively scheduled for next bug fix releases. |
Modified by: @mrotteveeldescription: Add a property url on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration. For some reason this property seems to be required to exist by either Spring JPA or Hibernate. See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for an example. For now tentatively scheduled for next bug fix releases. => Add a property url on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration. See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for an example. For some reason this property seems to be required to exist by either Spring JPA or Hibernate, or maybe by the code used by the OP. For now tentatively scheduled for next bug fix releases. |
Modified by: @mrotteveeldescription: Add a property url on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration. See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for an example. For some reason this property seems to be required to exist by either Spring JPA or Hibernate, or maybe by the code used by the OP. For now tentatively scheduled for next bug fix releases. => Add a property url on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration. See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for an example. For some reason this property seems to be required to exist by either Spring JPA or Hibernate, or maybe by the code used by the OP. For now tentatively scheduled for next bug fix releases, this may change if it turns out to be a problem with this specific code. |
Modified by: @mrotteveelFix Version: Jaybird 3.0.5 [ 10873 ] Fix Version: Jaybird 3.0.4 [ 10861 ] => |
Commented by: @mrotteveel As it was actually user error, I will defer this to Jaybird 5 |
Modified by: @mrotteveelFix Version: Jaybird 5 [ 10871 ] Fix Version: Jaybird 3.0.5 [ 10873 ] => Fix Version: Jaybird 2.2.15 [ 10860 ] => Fix Version: Jaybird 4 [ 10441 ] => |
Decided not to do this. |
Submitted by: @mrotteveel
Add a property url on (relevant) data sources, which accepts a JDBC url (including connection properties), and parses it to relevant configuration.
See https://stackoverflow.com/questions/48911266/proper-setup-of-jaybird-firebird-datasource-with-hikaricp for an example. For some reason this property seems to be required to exist by either Spring JPA or Hibernate, or maybe by the code used by the OP.
For now tentatively scheduled for next bug fix releases, this may change if it turns out to be a problem with this specific code.
The text was updated successfully, but these errors were encountered: