http://debianws.lexgopc.com/wiki143/index.php?action=history&feed=atom&title=Persistent_programming_languagePersistent programming language - Revision history2026-10-25T04:14:48ZRevision history for this page on the wikiMediaWiki 1.43.1http://debianws.lexgopc.com/wiki143/index.php?title=Persistent_programming_language&diff=1826652&oldid=previmported>JoeNMLC: chg unref. to refimprove tag2025-02-05T20:34:09Z<p>chg unref. to refimprove tag</p>
<p><b>New page</b></p><div>{{Issues|<br />
{{technical |Computer science |date=January 2025}}<br />
{{Refimprove|date=February 2025}}<br />
}}<br />
[[Programming language]]s that natively and seamlessly allow [[Object (computer science)|object]]s to continue existing after the [[computer program|program]] has been closed down are called '''persistent programming languages'''. [[JADE programming language|JADE]] is one such language.<br />
<br />
A persistent programming language is a programming language extended with constructs to handle persistent data. It is distinguished from embedded SQL in at least two ways: <br />
<br />
In a persistent programming language:<br />
<br />
* The query language is fully integrated with the host language and both share the same [[type system]].<br />
* Any format changes required between the host language and the database are carried out transparently. <br />
<br />
In Embedded SQL:<br />
<br />
* Where the host language and [[data manipulation language]] have different type systems, code conversion operates outside of the OO type system, and hence has a higher chance of having undetected errors. <br />
* [[Format conversion]] must be handled explicitly and takes a substantial amount of code.<br />
<br />
Using Embedded SQL, a programmer is responsible for writing explicit code to fetch data into memory or store data back to the database. <br />
In a persistent programming language, a programmer can manipulate persistent data without having to write such code explicitly. <br />
<br />
The drawbacks of persistent programming languages include:<br />
<br />
* While they are powerful, it is easy to make programming errors that damage the database.<br />
* It is harder to do automatic high-level optimization.<br />
* They do not support declarative querying well.<br />
<br />
==Examples==<br />
<br />
* [[MUMPS]]<ref name="MUMPS1969">{{cite journal |last1=Greenes |first1=Robert |last2=Pappalardo |first2=A Neil |last3=Marble |first3=Curt W |last4=Barnett |first4=G Octo |title=Design and implementation of a clinical data management system. |journal=Comput Biomed Res |date=1969 |volume=5 |issue=Oct |pages=469–85 |doi=10.1016/0010-4809(69)90012-3 |pmid=11697375 }}</ref><br />
* [[JADE programming language|JADE]]<ref>{{cite web|url=https://www.zdnet.com/article/jade-delivers-version-7-1/|title=Jade Software delivers Jade 7.1|publisher=[[ZDnet]]|accessdate=21 December 2019}}</ref><br />
* [[Caché ObjectScript]]<ref>{{Cite web|url=https://cedocs.intersystems.com/latest/csp/docbook/Doc.View.cls?KEY=TCOS_Quit|title = Quit Command &#124; ObjectScript Tutorial &#124; Caché & Ensemble 2018.1.4 & 2018.1.5}}</ref><br />
<br />
==See also==<br />
* [[Object-relational mapping]]<br />
* [[Object-oriented database management system]]s<br />
* [[Object prevalence]]<br />
* [[Phantom OS]] - persistent OS project<br />
<br />
==References==<br />
{{reflist}}<br />
<br />
{{comp-sci-stub}}<br />
<br />
[[Category:Programming language classification]]<br />
[[Category:Persistent programming languages]]</div>imported>JoeNMLC