In today’s article, we will take a look at composite primary key support in two top Java ORMs: jOOQ and Hibernate. We’ll look at a couple examples, learn how column configuration looks in Hibernate, and how support is organized in jOOQ.
Object-Relational Mapping (ORM) is a library which converts data between a relational database and an object-oriented language. Vertabelo Mobile ORM is specifically designed for mobile app developers working in Android and iOS and using SQLite databases. It’s simple: Vertabelo uses graphical data models to automatically generate classes – Data Access Objects (DAOs) and others – to provide simplified access to data stored in an app’s SQLite database.
The most common way to implement database functionalities in iOS applications is definitely Apple’s Core Data. However, its architecture is really Apple-like: it doesn’t let you see anything happening inside and the structure is hidden from you. That’s why some people dislike Core Data and prefer to stick with an SQLite database – even though SQLite is not supported natively.
Although mobile apps do not rely on databases as much as, say, web applications, mobile app developers should still be interested in databases. There are better database solutions for Android apps than a native SQLite library; we’ll nominate ORMs as one of them. In this article, we’re going to take a look at some of the most popular Android ORMs: ORMLite, ActiveAndroid, greenDAO, and Sugar ORM. We’ll also check out our new Vertabelo Mobile ORM.
We’ve had tremendously positive feedback on my recent article that talked about the awesomeness of SQL. However, not everyone agreed to the Fallacy #5: The database is the wrong place for business logic. Why is this such a controversial topic? In what situations is the database the right place, and in what situations isn’t it the right place for such logic?
I’ve been testing a ton of frameworks lately – good and otherwise. One of them, the Java micro framework Spark, really amazed me with its simplicity and rapid development capabilities. In this article, we’ll examine an example of Spark’s usefulness by creating a REST API. So, without further ado, let’s see how to store, retrieve, update and delete some information in a PostgreSQL database using jOOQ ORM over a RESTful API in a simple To-do app.
jOOQ is a Java Object-Relational Mapper that lets you build type safe SQL queries through its fluent API. Using built-in Vertabelo support we can generate sufficient code from the previously designed model. Generated Java classes correspond to database tables, records, etc. This time, we automate this process by using Gradle build system.
jOOQ provides an easy way to automate the process of generating the java classes that represent database tables, records, etc. via the jooq-codegen-maven plugin. This time we let Maven worry about downloading the required JAR files and generating Java code that lets you build typesafe SQL queries through jOOQ’s fluent API.
It often happens that if something is loved, it is also hated with the same power. The idea of object relational mapping fits into this concept perfectly. You will definitely come across many opposite points and fierce discussions as well as unwavering advocates and haters. So if you have ever asked whether to use ORM or not, the answer “it depends” will not be enough.
jOOQ and Vertabelo perfectly complement each other in the application development. With Vertabelo you can easily design a database structure what saves you from writing DDL code manually, while jOOQ handles generation of Java classes corresponding to database tables, and allows to construct SQL queries through its fluent API.