What is the best way to store scripts?
-
My Definitions: script: A script contains one or more executable records which may also include other scripts. executable record: An executable record contains a header and a data section. data section contains a struct representing the values of the executableID. (currently the data section is binary data that gets converted by the script engine) header contains sourceID, executableID, sizeof(header + data section). I have thousands of modular scripts that do specific tasks and that could be used by other scripts. For example: MainScript01 -DoSomethingA -DoSomethingB -DoSomeThingC MainScript02 -DoSomethingA -DoSomethingD --DoSomethingC I would like to view the scripts in a tree. I would like to store the scripts in a database or other text based container. If possible in ASCII format for easy editing outside the script engine application. Question: What are some specific possibilities that I could use to store scripts? I am trying to figure out what type of table(s) and fields I should have. -one table holds them all? (cannot easily update structures in the Data field) table definition: ScriptID, ScriptRecordNo, TotalRecords (in this ScriptID), Comments, Data (byteArray of executableID), Index (automatically generated by database), (other control fields) -separate tables? -Mainscripts (using foreign keys to subscripts and executableIDs?) -subscripts (using foreign keys to subscripts and executableIDs?) -each type of executableIDs (one field for variable in the struct makes changing structs and values easier) I would like some pros and cons if possible. Thanks
Michael ﾠﾠﾠﾠﾠﾠﾠﾠﾠ\|/ ﾠﾠﾠﾠﾠﾠﾠ^O^O^ ——o00o—0—o00o—— If we knew what it was we were doing, it would not be called research, would it? --Albert Einstein
modified on Tuesday, February 10, 2009 11:10 AM