I have a spring project and I would like very much to use Spring Data OrientDB, is it production ready? or should I just use Graph API or blueprints? 

Is Spring Data OrientDB production-ready?

I have written below java code in my JPA repository.

@Query("insert into table (date_colum) value(:dateValue)",nativeQuery= true)
public int insertData(@Param("dateValue") dateValue);


Above code is working perfect when dateValue column is having some value. But when value of dateValue cloumn is null in that case it will giving the below error .

Error : ora-00932 inconsistent datatypes expected date got binary


Any solution please , help is appreciate.

If We add @Temporal to your Date parameter, Spring Data knows how to present that parameter to Hibernate, even if it is null:

@Query("insert into table (date_colum) value(:dateValue)",nativeQuery= true)

public int insertData(@Param("dateValue") @Temporal java.util.Date dateValue);

JPA @query is not working when date value is null during insert

I'm creating a couple of NamedEntityGraphs in my Entity. I have been able to stop JPA from joining other tables by not including the attribute in the NamedAttributeNode.

But for the rest of attributes like dates, strings, etc they will always appear in the query generated by Hibernate.

How can I prevent hibernate from selecting those columns?

Please don't tell me to ignore it in the view layer, the point of not fetching the rest of the columns is for optimization of the query/network.

Also I know I can use @Query in my spring repository but I want to keep my repositories clean.

And the same goes for not creating new entity classes with fewer attributes, I want to reuse the entities.

The most common way of not selecting certain attributes is to use a native SQL query that only selects the columns you want, e.g.

@Query(value = "SELECT col1, col2 FROM some_table", nativeQuery = true)

List<Object[]> findOnlyTwoColumnsFromTable();

Instead of using List<Object[]>, you might also be able to define a DTO class that just has two fields in it, e.g. List<TwoColumnDTO>.

This may look messy, and certainly, it is less clean than neatly using pure JPA to select into an entity class. But the thing to remember here is that the JPA methods are, at the end of the day, merely convenience methods. If they serve your purpose well, then use them. Otherwise, for most of your applications you will typically end up with a few native queries here and there, and there is nothing wrong with it.

How to ignore attributes from being SELECTed in JPA NamedEntityGraph?

Mongodb offers the possibility to avoid over-fetching of data via projection so select only what you wont to have from fields of the document... GraphQL is offering the user the possibility to select only what he wont to have from API fields.

Is there any way based on java (spring) to forward the selected user input (from DataFetchingEnvironment) to mongodb (Query) because the API and document (collection) are almost the same...

spring-data

Trending Blogposts on spring-data

Popular Discussions on spring-data

openIs Spring Data OrientDB production-ready?

1

0

0

openJPA @query is not working when date value is null during insert

3

1

0

openHow to ignore attributes from being SELECTed in JPA NamedEntityGraph?

2

1

0

openspring graphq avoid mongodb data overfetching

1

0

0

PRODUCTS

QUICK LINKS

LEGAL