Source Code in Database

This article has multiple issues. Please help improve it or discuss these issues on the talk page . (Learn how and when to remove these messages)

The topic of this article may not meet Wikipedia's general notability guideline . Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.
Find sources: "Source Code in Database" – news · newspapers · books · scholar · JSTOR (April 2013) (Learn how and when to remove this message)

This article needs additional citations for verification . Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Source Code in Database" – news · newspapers · books · scholar · JSTOR (January 2021) (Learn how and when to remove this message)

(Learn how and when to remove this message)

Source Code in Database (SCID) is a technique of code manipulation where the code is parsed and stored in a database. This allows many productivity-enhancing shortcuts^{[clarification needed ]} which were otherwise not possible.

A drawback of SCID systems is that code with syntax errors or other code that cannot be parsed^{[clarification needed ]}, cannot be imported into a SCID system directly. One workaround for this is to comment out code that doesn't parse correctly.

Visual programming tools may store programs as databases, since specialized structure editors are required to edit visual code.

Examples

[edit ]

IBM VisualAge Java is an example of an integrated development environment implementing SCID features. A more recent example of Source Code in Database is CodeOntology, an open source tool and RDF database of Java source code that supports advanced SPARQL queries, such as Select recursive methods or Select methods that compute the cube root of a double.^[1]