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

Timeout if sql takes more than 2 seconds to execute #66

Closed
shdatta opened this issue Nov 14, 2016 · 2 comments
Closed

Timeout if sql takes more than 2 seconds to execute #66

shdatta opened this issue Nov 14, 2016 · 2 comments

Comments

@shdatta
Copy link

shdatta commented Nov 14, 2016

Hi, I am using latest version of exposed and I was getting following
warning WARN 70808 --- [pool-2-thread-1] Exposed : Long query: [2113ms] .

I am OK with my query taking more than 2 seconds to execute. But it looks like this is hard coded in Transaction.kt in variable warnLongQueriesDuration and I get exception. Can you make this configurable or is there any other way around.

Thanks

Tapac added a commit that referenced this issue Nov 15, 2016
 warnLongQueriesDuration is optional now
@Tapac
Copy link
Contributor

Tapac commented Nov 15, 2016

I've made warnLongQueriesDuration an optional, so you have to initialize it implicit if you want to use that kind of a warning.
Before that change will be released you can set this variable to some large value within your transaction{ } block to prevent a warning.

@Tapac Tapac closed this as completed Nov 15, 2016
@shdatta
Copy link
Author

shdatta commented Nov 16, 2016

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants