All the Perl that's Practical to Extract and Report
use Perl Log In
hydo (2599)
Friday April 18, 2003
03:44 AM
SQL-Ledger
I really really really should have looked at the code for this a little closer before I agreed to add a few bits of functionality to it. It was probably my enthusiasm about being paid once again to code that got me in trouble.
*Much later after I noticed this tab in Safari*
I guess it's not so bad. I mean, it IS bad, but not as "blood gushing from the eyes" bad as I thought at first. Any web app that uses a frontend script to exec() another script based on user input needs a dose of CGI::Application or some such module. I hope I can find my copy of the rhino book.
SQL-Ledger
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
world like English did. Er, *as* English did...
--Larry Wall in <199705201832.LAA28393@wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
SQL Ledger Issues (Score:2)
While I am impressed with its list of features, I am less than impressed with its quality. I did an internal review of this product for where I work and I found a few problems [perlmonks.org]. Unfortunately, I was taken to task for this [geocrawler.com] and the lead developer referred to my concerns as being "nonsense". That was interesting because I merely listed my conclusions, but not how I arrived at them.
I would love to see SQL Ledger be turned into a good, solid product that I'm not afraid to touch. (psst ... maybe you want to
Re:SQL Ledger Issues (Score:1)
On the one hand, I should have read this before my meeting and been prepared to give a more accurate estimate. On the other hand, learning this package and getting the functionality they want by Monday is proving to be a fun challenge that I am enjoying more