Hibernate Native SQL

vembubalaji

61.1K views

GitHub

Open Source Your Knowledge, Become a Contributor

Technology knowledge has to be shared and made accessible for free. Join the movement.

Create Content

Previous: Use parameter binding in native SQL queries Next: Native Joins

Adding scalars

To avoid the overhead of using ResultSetMetadata, or simply to be more explicit in what is returned, we use scalars while creating Native Queries

A quick sample. Check out the JAVA class and SQL file

// {
        List<Object[]> domain = session.createNativeQuery("SELECT * FROM domain")
                .addScalar("domain_id", IntegerType.INSTANCE).addScalar("domainName", StringType.INSTANCE).list();
        domain.stream().forEach(objects -> {
            Integer id = (Integer) objects[0];
            String name = (String) objects[1];
            System.out.println(String.format("Info: Domain[ %d, %s ]", id, name));
        });
    }

In this case, only domain_id and domainName would be returned back, though, we have requested for * from the table.
Also, we would still be returned with an array of Object – List<Object[]>, but now it will not use the ResultSetMetadata to determine the type of columns, but will instead explicitly get the domain_id, and domainName column as respectively a Integer, and a String from the underlying resultset.
Adding scalars to native Queries is preferable, considering the reduced overhead on the ResultSetmetaData and a marginal improvement on the performance.

Open Source Your Knowledge: become a Contributor and help others learn. Create New Content

Open Source Your Knowledge, Become a Contributor

3/8 Adding scalars

Adding scalars

PYTHON: BEGINNER QUIZ (10 Questions)

Stored Procedures con T-SQL

PYTHON STRING METHODS: center(), rjust() and ljust().

Online Voting Concept