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

Option to have PRINT output show up in logs #68

Closed
Jaykul opened this Issue Jul 26, 2012 · 6 comments

Comments

Projects
None yet
3 participants
@Jaykul

Jaykul commented Jul 26, 2012

A lot of scripts have debugging-style PRINT statements in them (e.g. usp_GetDate.sql and 003_AppPermissionsWiring.sql from the sample). We need an option to have the output of those PRINT statements show up in console/log output when they're run by RoundhousE.

At least in SQL and Oracle it should just be a matter of handling the InfoMessage event on the connection (it's not on the base class, and I don't know anything about your other databases...) http://www.dotnetcurry.com/ShowArticle.aspx?ID=344

@ghost ghost assigned ferventcoder Aug 9, 2012

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Aug 9, 2012

Member

Super awesome - this is going into 0.8.6 or the next release

Member

ferventcoder commented Aug 9, 2012

Super awesome - this is going into 0.8.6 or the next release

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Sep 7, 2012

Member

This looks really interesting...when run.

Member

ferventcoder commented Sep 7, 2012

This looks really interesting...when run.

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Sep 7, 2012

Member

Not sure yet if I like it or think it is getting too verbose. Right now the statements are running at INFO level, which is what all of the other messages run at.

Member

ferventcoder commented Sep 7, 2012

Not sure yet if I like it or think it is getting too verbose. Right now the statements are running at INFO level, which is what all of the other messages run at.

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Sep 7, 2012

Member

Fixed in 39ce6b4

Member

ferventcoder commented Sep 7, 2012

Fixed in 39ce6b4

GoogleCodeExporter pushed a commit to google-code-export/roundhouse that referenced this issue Mar 13, 2015

@ferventcoder ferventcoder modified the milestone: 0.8.6 Jun 3, 2015

ChrisMissal pushed a commit to ChrisMissal/roundhouse that referenced this issue Jul 30, 2015

@jzabroski

This comment has been minimized.

Show comment
Hide comment
@jzabroski

jzabroski Aug 7, 2015

This is great, but what we really need bubbling back to the logger are all User Error Message events. Some of these get swallowed right now.

I would break the debug flag into multiple levels. That's what most *NIX utilities do.

This is great, but what we really need bubbling back to the logger are all User Error Message events. Some of these get swallowed right now.

I would break the debug flag into multiple levels. That's what most *NIX utilities do.

@ferventcoder

This comment has been minimized.

Show comment
Hide comment
@ferventcoder

ferventcoder Aug 7, 2015

Member

@jzabroski Do you want to add a new ticket? I don't think we realized that some get swallowed. Definitely not what we want to happen.

Member

ferventcoder commented Aug 7, 2015

@jzabroski Do you want to add a new ticket? I don't think we realized that some get swallowed. Definitely not what we want to happen.

jvopalensky pushed a commit to firmwater/roundhouse that referenced this issue Jun 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment