Re: [Andy.] build error help!!
Andy, Lennie,
The config has 3 debugging levels:
This method returns the current debug level.
You may provide one argument which sets a new debug level.
0 means no debugging, 1 means basic debugging, 2 means heavy debugging.
If providing a new debug level, the old debug level is returned.You can check this in Developers Guide/GT::Config.
The following is not required for you, Andy, but may be useful for later usage. Just for your information.
There are 4 debug levels for GT::SQL (sql related queries):
def_path => '/path/to/def',
cache => 1,
debug => 1,
subclass => 1
);
...
GT::SQL has advanced debugging, and setting it to 1 should be adequate for most operations.
Level 0
This is the default, no debugging information is printed to stderr. All errors can be obtained in $GT::SQL::error.
Level 1
All queries that get sent will be displayed to stderr.
Level 2
Same as level 1, but more detailed information. Also, when calling query_stack you get a stack trace on what generated each query.
Level 3
Very detailed debug logs including creation and destruction of objects. query_stack generates a javascript page with query, stack trace plus data dump of arguments, can be very, very large (but very cool).You can check this in Developers Guide/GT::SQL.
I hope this helps.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
The config has 3 debugging levels:
Quote:
debug_level This method returns the current debug level.
You may provide one argument which sets a new debug level.
0 means no debugging, 1 means basic debugging, 2 means heavy debugging.
If providing a new debug level, the old debug level is returned.
The following is not required for you, Andy, but may be useful for later usage. Just for your information.
There are 4 debug levels for GT::SQL (sql related queries):
Quote:
$db = new GT::SQL { def_path => '/path/to/def',
cache => 1,
debug => 1,
subclass => 1
);
...
GT::SQL has advanced debugging, and setting it to 1 should be adequate for most operations.
Level 0
This is the default, no debugging information is printed to stderr. All errors can be obtained in $GT::SQL::error.
Level 1
All queries that get sent will be displayed to stderr.
Level 2
Same as level 1, but more detailed information. Also, when calling query_stack you get a stack trace on what generated each query.
Level 3
Very detailed debug logs including creation and destruction of objects. query_stack generates a javascript page with query, stack trace plus data dump of arguments, can be very, very large (but very cool).
I hope this helps.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...