Larry, I really like that you used the word "miscreants". I seem to recall an old RBExchange (or some other earlier RB-info source) where a "simulated" R> was described/implemented. If my recall is good, was what you did in any way related to that?
Sorry to that there is an implication in your message that there is the persistent existence of miscreants, but nice vocab', dude. Steve -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lustig Sent: Friday, February 29, 2008 11:41 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Seeking Advice On Storing/Saving Statements in Database << So, would anyone have advice regarding this, especially with regard to my basic design and/or your experiences having done something similar? >> Some time ago I did a "proof of concept" of a fake R> prompt in which the user would type in an SQL statement in a memo field, the statement would be checked, executed, and stored, and the results displayed in a larger memo field below. It functioned very much like the regular R> prompt except that a statement that took some time to execute (like a long, slow SELECT) would not display ANY results until execution was finished (output was sent to a file, then the file was loaded into the memo field). The only way in which it differs from what you layed out is that I didn't include a separate keyword table, but I did provide for the username to be stored with the statement so people could have private SQL libraries. The purpose was three-fold: to stop users from executing certain statements (eg "vSQL LIKE 'DEL%'"), to log all SQL executed to find certain miscreants, and to begin to build a library of common SQL to help us determine what functions could most productively be automated. I never put it into production although I have a feeling it's going to be revived sometime soon. If it does get done, I can probably share the work. -- Larry
