#1923 ✓resolved
Guylian Pot

Multidb configuration glitches

Reported by Guylian Pot | February 16th, 2015 @ 01:27 PM | in 1.3.1 (closed)

Framework version: 1.3.0
Platform you're using: Windows

Reproduction steps:

  • Have a multidb setup, where one is named and the other not (so db.driver=com.mysql.jdbc.Driver and db.example.driver=com.mysql.jdbc.Driver)
  • Add jpa.debugSQL=true
  • Observe no query output in the log after triggering one
  • Replace with jpa.default.debugSQL=true
  • Observe no query output in the log after triggering one
  • Add jpa.example.debugSQL=true
  • Observe query output in the log after triggering one

Details:
I also had a hibernate.use_sql_comments=true config key that didn't work until the last step, after which I started to get the comments for the default db. After the last step, I can rename jpa.default.debugSQL=true back to jpa.debugSQL=true and it will still work. However, if I set jpa.example.debugSQL=false, it stops the query output for both DBs again.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Pages