From: Dave S. <bou...@ya...> - 2006-11-13 18:31:58
|
--- Mark Bucciarelli <ma...@ga...> wrote: > On Sun, Nov 12, 2006 at 08:13:13PM -0800, Dave Snell > wrote: > > By hitting the db directly, you will end up > duplicating some > subset of the application logic; for example, is > customer ID > valid, is part number valid, is part number active, > etc, etc. > > As app logic and/or table structure changes, you may > need to > update your script. This could be painful and will > be > error-prone. > > If (by some small chance) you insert data that > doesn't satisfy > the app's assumptions re: data integrity, who knows > what kind of > wierd bugs you could create. > > Makes it much harder for Dieter to give you good > support as well. > If I was him I wouldn't support this at all. > > Yeah, not using the API will make your scripts > marginally faster > but it doesn't seem worth it. I take it you're not a Perl developer. By using LWP I wouldn't be skipping any of the application's edits, I wouldn't be violating any referential integrity rules, and I shouldn't end up with duplicate anything - as I wouldn't be hitting the database directly. LWP is a "set of Perl modules which provides a simple and consistent application programming interface (API) to the World-Wide-Web". In otherwords, I'd still be using the application, it would just be a Perl program that was stepping through the screens. Not me, or one of my staff. B ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited |