I think I've seen something somewhere related to this, but I wanted to ask about it.
I would like to begin saving "work-in-process" statements to my database. Essentially, these are DEV/TEST/"one-off" statements executed from the R>. Historically, I've just saved them by copying-n-pasting from the R> to RBedit files, named along the lines of "SQL_2DAY_CCYYMMDD.TXT". However, even with comments, I am now finding this approach FAR less than optimal. So, my thinking to this point is that I'll need one table to hold the statements and comments and a related "many-side" table to hold keywords for searches. Maybe : SQL_2DAY StatementPK INT (AUTONUM) StatementString TEXT? (??) StatementComments NOTE? StatementCreateDate DATE StatementCreateTime TIME SQL_2DAY_KEYWORDS StatementPK INT (FK) Keyword TEXT (??) (PK: StatmentPK & Keyword) So, would anyone have advice regarding this, especially with regard to my basic design and/or your experiences having done something similar? Thanks, Steve in Memphis J. Stephen Wills Program Manager, Research Informatics Office of the Vice Chancellor for Research University of Tennessee Health Science Center 62 S. Dunlap, Suite 400 Memphis, TN 38163 Office: 901-448-2389 FAX : 901-448-7133
