Home > Articles > Data > MySQL

End-to-End JPA Collections with MySQL, Part 2

Having difficulty modifying your JPA collection code? Do you think stored procedures are very complicated? Stephen Morris provides simple, end-to-end working code illustrating how to modify JPA collection code. Also, the area of MySQL stored procedures is looked at, using some simple examples in this the concluding part of a two-part series.
Like this article? We recommend

Like this article? We recommend

As programmers, we have to try to keep up to date as technology changes. The area of databases in general and object relational mapping (ORM) in particular are good examples of such areas. Indeed, ORM underpins many of the most popular frameworks, such as Spring, EJB3, etc.

I've often thought that the greatest skill in programming lies not in writing new code but in modifying existing or legacy code. Many of us prefer to write new code rather than delve into old code. Very often, the author of the legacy code may have left the organization or is too busy to help, or has even forgotten how the code works!

I recall one case where a departed contractor had written some extremely complex code that was failing. After sifting through many pages of source code, I noticed that there was a comment indicating that most of the code had been downloaded from a forum by the contractor and that he was at a loss to understand it. Not something to inspire confidence as a large chunk of code had to be excised and rewritten to fix the original problem.

Regardless of the ownership of the code, in many cases, the underlying business is generally built on legacy code. So, learning to change code may in fact be a more critical skill than writing greenfield code.

In this, the second of a two-part article series, I'll be demonstrating how to extend an existing (or legacy) collection-based JPA model. The model used comes from Part 1, where we built a simple JPA unidirectional one-to-many mapping. To conclude Part 2, I'll also look at an important server-side technology: stored procedures in the context of MySQL.

A One-to-Many Unidirectional Collection

In Part 1, you saw an example of a simple entity that contains a collection as illustrated in Listing 1.

Listing 1—A Department Entity Containing a Collection of Persons

@Table(name = "DEPARTMENT")
        query="select OBJECT(d) from Department d where d.name = :name")
public class Department implements Serializable {
    private static final long serialVersionUID = 1L;
    @Id @GeneratedValue(strategy=GenerationType.IDENTITY)
    @Column(name = "DEPT_ID")
    private Long id;
    @Column(name = "name", unique=true)
    private String name;
    private List<Person> persons = new ArrayList<Person>();
    public Department() {
    public Department(String name) {
        this.name = name;
    public Long getId() {
        return id;
    public String getName() {
        return name;
    public void setName(String name) {
        this.name = name;
    @OneToMany(cascade=CascadeType.ALL, mappedBy="department")
    public List<Person> getPersons() {
        return persons;
    public void setPersons(List<Person> persons) {
        this.persons = persons;
    public String toString() {
        return "Department [id=" + id + ", name=" + name + "]";

You can see from the line

private List<Person> persons = new ArrayList<Person>();

that the Listing 1 Department entity contains a collection of class Person. This is coded as a one-to-many unidirectional relationship. Nothing too complicated there. Indeed, the magic of annotations provides extraordinary power in transforming a piece of Java code into a rich and complex piece of database modelling and persistence logic.

Let's now imagine that a new business requirement arises and you want to extend the entity relationship in Listing 1—e.g., suppose we wanted to change this from a unidirectional relationship into a bidirectional one. It's not too hard to do this—in fact, just three changes are needed to the following:

  • SQL code
  • Person code
  • Adding a person to a department code

Let's start with the SQL code because it's a relatively simple change. Listing 2 illustrates the modified SQL code.

Listing 2—A Change to the PERSON Table DDL

CREATE TABLE `quickstart`.`PERSON` (
  `firstName` VARCHAR(45) NOT NULL,
  `lastName` VARCHAR(45) NOT NULL,
  `friends` VARCHAR(45) NOT NULL,
  `DEPARTMENT_DEPT_ID` int unsigned,

Can you see the change to the SQL? Well, I've simply added a new column called DEPARTMENT_DEPT_ID, which is a foreign key on the DEPT_ID from the DEPARTMENT table. This establishes a relationship between the rows in the PERSON table and the rows in the DEPARTMENT table.

The other required change is the addition of a new annotated @ManyToOne Department field to the Person Java class, as illustrated in Listing 3.

Listing 3—Modifying the Person Class

    private String friends;
    Department department;
    public Person() {

Each instance of the Person class must now maintain a Department instance field, and the multiplicity of this relationship is ManyToOne—i.e., there are potentially zero, one, or many persons in one department.

A useful thing to remember about JPA mapping is that the annotations should always make sense—i.e., in this case you have potentially many persons in a given department. This is a simple litmus test for your mapping code.

One other required change to the Person class is a setter and getter method for the new field:

    public Department getDepartment() {
        return department;
    public void setDepartment(Department department) {
        this.department = department;

So, how do we test this relationship?

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020