Persistent programming language

Programming languages that natively and seamlessly allow objects to continue existing after the program has been closed down are called persistent programming languages. The only commercial product that appears to do this at the moment is JADE, but it is anticipated that persistent programming languages will become more popular in the future.

A persistent programming language is a programming language extended with constructs to handle persistent data. It distinguishes with embedded SQL in at least two ways: In a persistent program language, query language is fully integrated with the host language and both share the same type system. Any format changes required in databases are carried out transparently. Comparison with Embedded SQL where (1) host and DML have different type systems, code conversion operates outside of OO type system, and hence has a higher chance of having undetected errors; (2) format conversion takes a substantial amount of code.

Using Embedded SQL, a programmer is responsible for writing explicit code to fetch data into memory or store data back to the database. In a persistent program language, a programmer can manipulate persistent data without having to write such code explicitly.

Drawbacks: (1) Powerful but easy to make programming errors that damage the database; (2) harder to do automatic high-level optimization; and (3) do not support declarative querying well.

ee also

* Object-relational mapping
* Object-oriented database management systems