★ wanayoo — archive 1999 https://github.com/utPLSQL/utPLSQL/issues/480Nouvelle recherche | Portail wanayoo
Skip to content

/ utPLSQL

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

Jump to bottom

Improve/modify debug logging #480

Closed
jgebal opened this issue Aug 31, 2017 · 3 comments
Closed

Improve/modify debug logging #480

jgebal opened this issue Aug 31, 2017 · 3 comments
Labels
enhancement
Milestone
v3.1.4

Comments

@jgebal
Copy link
Member

@jgebal jgebal commented Aug 31, 2017

Currently to debug-log the framewor we need to compile it for debug, also the debug-logging is incomlete.

We could add logging levels of 1-5 where 1 is info 5 is with variables.

We could maybe use some of existing logging frameworks to save logs.

Any thoughts?
@jgebal jgebal added the enhancement label Aug 31, 2017
@jgebal jgebal changed the title Improve/modufy debug logging Improve/modify debug logging Aug 31, 2017
@mathewbutler
Copy link

@mathewbutler mathewbutler commented Aug 31, 2017

OraOpenSource/logger on GitHub maybe?

I've heard good things but never used. I believe it's a robust implementation similar to Connor MacDonalds debug package from his PLSQL book.
@Shoelace
Copy link
Member

@Shoelace Shoelace commented Sep 5, 2017

can I suggest the log4 style Shoelace/log4oracle
it is quite "heavy" to but has drop-in singleobject/lite implementation that can be customised as need by

FYI. its one i have written. and I'm still trying to finish the update to log4 v2 but I just haven't had much time lately (for that or utplsql :( )
@jgebal
Copy link
Member Author

@jgebal jgebal commented Feb 5, 2018 •
edited

I think we first should address #523
In general I don't use the current debug logging at all - it's of no value to me currently so maybe we should think of logging user-level warnings only?
@jgebal jgebal mentioned this issue Mar 15, 2019
Merged
@jgebal jgebal added this to the v3.1.4 milestone Mar 15, 2019
@jgebal jgebal closed this in #857 Mar 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
v3.1.4
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@Shoelace @mathewbutler @jgebal
You can’t perform that action at this time.