Code Comments
Programming Forum and web based access to our favorite programming groups.>>> On 10/9/2007 at 6:41 PM, in message < GemdnaPKRcdMgpHanZ2dnUVZ_tLinZ2d@comcast .com>, LX-i<lxi0007@netscape.net> wrote: > Frank Swarbrick wrote: > > Do they have other database access classes? I don't think I'd *want* to > do EXEC SQL in a class unless I just had to... :) I don't know. I guess since they support instantiating Java objects from within COBOL you could use JDBC. I don't understand the reasoning behind your second statement, though. It seems to me (without having actual tried it!) that it would be desirable to have a database access class containing EXEC SQL statements. That is if you're stuck using static SQL, which I know Pete always comes out against. (I don't have enough experience to have an opinion on that matter). Assuming that you were working with mainframe COBOL and you, for whatever reason, are not using JDBC for database access, what type of OO methodology and database access would you use? I assume (perhaps erroneously!) that coding EXEC SQL statements in the main body of each program is not the best OO way to go. Then again, perhaps it is? Frank
Post Follow-up to this messagePowered by vBulletin
Copyright 2000-2006 Jelsoft Enterprises Limited.