首页 \ 问答 \ 要使用的Hibernate或JPA注释(Hibernate or JPA annotations to use)

要使用的Hibernate或JPA注释(Hibernate or JPA annotations to use)

 我在Hibernate Domain Pojo Objects的项目和基于注释的配置中使用Hibernate。 对于基于注释的配置，我们有两个选项  
 
  使用javax.persistence.*基于JPA的注释javax.persistence.*  
  使用Hibernate Native Annotations org.hibernate.annotations.*  
 
 目前，我们为POJO文件和Hibernate本机API（如SessionFactory，Session等）使用基于JPA的注释配置来打开会话并执行数据库操作。  
 在下面的事情需要你的帮助，  
 
  混合JPA注释和使用Hibernate本机API有什么问题吗？  
  这个链接解释了一个这样的问题（cascade-jpa-hibernate-annotation-common-wrong）  
  请提供您的专业知识，使用哪种注释 
   
    JPA  
    Hibernate原生  
    混合他们两个？  
   

I am using Hibernate in our projects and annotation based configuration for Hibernate Domain Pojo Objects. For Annotations based configuration we have two options  
 
 JPA based annotations using javax.persistence.* 
 Use Hibernate Native Annotations org.hibernate.annotations.* 
 
Currently we use JPA based annotation configuration for our POJO files and Hibernate native API like SessionFactory, Session, etc to open session and perform DB operations.  
I have these questions: 
 
 Is there any problem mixing both JPA annotations and use Hibernate native API? 
 This link explains one such issue (cascade-jpa-hibernate-annotation-common-mistake)  
 Please provide your expertise, which type of annotations to use 
   
   JPA  
   Hibernate native  
   Mix both of them? 
   

原文：https://stackoverflow.com/questions/16052347

更新时间：2021-09-06 20:09

最满意答案

 没有办法，因为conn.exec_params是本地C实现，并且返回的对象PG::Resul t也无法显示SQL。 如果你真的想看到这个查询，你可以在你的postgress配置中打开语句日志记录并查看它  
 然而，您可能会尝试查看是否有一些信息可用于错误常量中，但必须强制给出错误信息（请注意，我alpha_non_existent查询中的表名改为alpha_non_existent以强制错误）：  
begin
    resclose = conn.exec_params( %q{ SELECT * FROM alpha_non_existent WHERE pname ILIKE $1 ORDER BY id}, [submitted] )
rescue PG::Error => err
    p [
        err.result.error_field( PG::Result::PG_DIAG_SEVERITY ),
        err.result.error_field( PG::Result::PG_DIAG_SQLSTATE ),
        err.result.error_field( PG::Result::PG_DIAG_MESSAGE_PRIMARY ),
        err.result.error_field( PG::Result::PG_DIAG_MESSAGE_DETAIL ),
        err.result.error_field( PG::Result::PG_DIAG_MESSAGE_HINT ),
        err.result.error_field( PG::Result::PG_DIAG_STATEMENT_POSITION ),
        err.result.error_field( PG::Result::PG_DIAG_INTERNAL_POSITION ),
        err.result.error_field( PG::Result::PG_DIAG_INTERNAL_QUERY ),
        err.result.error_field( PG::Result::PG_DIAG_CONTEXT ),
        err.result.error_field( PG::Result::PG_DIAG_SOURCE_FILE ),
        err.result.error_field( PG::Result::PG_DIAG_SOURCE_LINE ),
        err.result.error_field( PG::Result::PG_DIAG_SOURCE_FUNCTION ),
    ]
end

There is no way because the conn.exec_params is a native C implementation, and the returned object PG::Result also has no way to show the SQL. If you really want to see the query you can turn on statement logging in your postgress configuration and have a look at it 
You might however try to see if there is some information you might use in the error constants, but you'll have to force an error to get it (note that I changed the name of the table in the query to alpha_non_existent to force an error): 
begin
    resclose = conn.exec_params( %q{ SELECT * FROM alpha_non_existent WHERE pname ILIKE $1 ORDER BY id}, [submitted] )
rescue PG::Error => err
    p [
        err.result.error_field( PG::Result::PG_DIAG_SEVERITY ),
        err.result.error_field( PG::Result::PG_DIAG_SQLSTATE ),
        err.result.error_field( PG::Result::PG_DIAG_MESSAGE_PRIMARY ),
        err.result.error_field( PG::Result::PG_DIAG_MESSAGE_DETAIL ),
        err.result.error_field( PG::Result::PG_DIAG_MESSAGE_HINT ),
        err.result.error_field( PG::Result::PG_DIAG_STATEMENT_POSITION ),
        err.result.error_field( PG::Result::PG_DIAG_INTERNAL_POSITION ),
        err.result.error_field( PG::Result::PG_DIAG_INTERNAL_QUERY ),
        err.result.error_field( PG::Result::PG_DIAG_CONTEXT ),
        err.result.error_field( PG::Result::PG_DIAG_SOURCE_FILE ),
        err.result.error_field( PG::Result::PG_DIAG_SOURCE_LINE ),
        err.result.error_field( PG::Result::PG_DIAG_SOURCE_FUNCTION ),
    ]
end

要使用的Hibernate或JPA注释(Hibernate or JPA annotations to use)

最满意答案

相关问答

gem pristine pg错误失败(gem pristine pg error fails)[2022-05-09]

Rails 3 - 无法安装pg gem(Rails 3 - can't install pg gem)[2023-06-15]

无法安装pg宝石(unable to install pg gem)[2023-07-22]

Ruby on Rails上的pg gem错误(pg gem error with Ruby on Rails)[2022-01-26]

调用postgres命令，如pg_restore或pg_dump，形成sql文件(Calling postgres command like pg_restore or pg_dump form sql file)[2023-04-06]

Ruby PG提交了SQL(Ruby PG Submitted SQL)[2023-11-08]

Ruby PG gem连接问题(Ruby PG gem connection issue)[2023-10-25]

从Ruby运行SQL脚本(Run sql script from Ruby)[2021-01-11]

使用SSL通过Ruby / PG gem在Redshift中“PG :: ConnectionBad：SSL错误：点不在曲线上”(“PG::ConnectionBad: SSL error: point is not on curve” in Redshift via Ruby/PG gem using SSL)[2022-03-29]

Ruby PG conn.exec_params SQL结构(Ruby PG conn.exec_params SQL structure)[2021-09-06]

相关文章

最新问答