Jakarta Persistence Query Language: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 22:56, 5 June 2023 edit Cngzz1 (talk \| contribs) Extended confirmed users 1,539 edits Fixed formatting issues. ← Previous edit		Latest revision as of 09:58, 29 July 2025 edit undo Onel5969 (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Rollbackers 992,997 edits m Disambiguating links to Object-orientation (link changed to Object-oriented programming) using DisamAssist.
(2 intermediate revisions by 2 users not shown)
Line 1: {{~~noref~~inline\|date=June 2010}} {{Infobox programming language \| name = Jakarta Persistence Query Language Line 20: \| website = }} The '''Jakarta Persistence Query Language''' ('''JPQL'''; formerly Java Persistence Query Language) is a platform-independent [[Object-oriented programming\|object-oriented]] [[query language]]{{sfn\|Bauer\|King\|Gregory\|2016}}{{rp\|loc=§12\|p=284}} defined as part of the [[Jakarta Persistence]] (JPA; formerly Java Persistence API) specification. JPQL is used to make queries against entities stored in a relational database. It is heavily inspired by [[SQL]], and its queries resemble SQL queries in syntax,{{sfn\|Bauer\|King\|Gregory\|2016}}{{rp\|loc=§1.3\|p=17}}, but operate against JPA entity objects rather than directly with database tables.{{sfn\|Bauer\|King\|Gregory\|2016}}{{rp\|loc=§2.2.3\|p=26}} In addition to retrieving objects (<code>SELECT</code> queries), JPQL supports set based <code>UPDATE</code> and <code>DELETE</code> queries.