.java:606)

            at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122)

           ... 75 more

Caused by: org.hsqldb.HsqlException: integrity constraint violation: NOT NULL check constraint; SYS_CT_10083 table: JOB column: ID

            at org.hsqldb.error.Error.error(Unknown Source)

            at org.hsqldb.Table.enforceRowConstraints(Unknown Source)

            at org.hsqldb.Table.insertSingleRow(Unknown Source)

            at org.hsqldb.StatementDML.insertSingleRow(Unknown Source)

            at org.hsqldb.StatementInsert.getResult(Unknown Source)

            at org.hsqldb.StatementDMQL.execute(Unknown Source)

            at org.hsqldb.Session.executeCompiledStatement(Unknown Source)

            at org.hsqldb.Session.execute(Unknown Source)

           ... 82 more

A:

Having simplified the application considerably, I established that this exception was a side-effect of having 2 entities referencing the same table, where the second table did have a field called "id".
i.e. 
@Entity
@Table(name = "my_table")
public class MyEntity {
    @Id @Column(name = "pk") private Long id;
   ...
}

@Entity
@Table(name = "my_table")
public class MyOtherEntity {
    @Id @Column(name = "id") private Long id;
   ...
}

It looks to me as though this caused Hibernate/JPA to generate and validate against a table which was a composite of the two entities, where (in the above example) "pk" and "id" were both non-null fields, and (perhaps due to being alphabetically later) the primary key was set to be the @Id of MyOtherEntity.
I'm not sure whether this is by design. Certainly, I can see that having multiple small entities referencing a huge flat table, might be useful when working with a 'legacy' database. But it certainly caught me out. Especially with the manner in which it treated the 2 separate @
.java:606) 

             at org.hibernate.engine.jdbc.internal.proxy. AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122) 

           ... 75 more 

 Caused by: org.hsqldb. HsqlException: integrity constraint violation: NOT NULL confirmation restraint; SYS_CT_10083 table: JOB column: ID 

             at org.hsqldb.error. Error.error(Unknown Source) 

             at org.hsqldb. Table.enforceRowConstraints(Unknown Source) 

             at org.hsqldb. Table.insertSingleRow(Unknown Source) 

             at org.hsqldb. StatementDML.insertSingleRow(Unknown Source) 

             at org.hsqldb. StatementInsert.getResult(Unknown Source) 

             at org.hsqldb. StatementDMQL.execute(Unknown generator) 

             at org.hsqldb. Session.executeCompiledStatement(Unknown Source) 

             at org.hsqldb. Session.execute(Unknown Source) 

           ... 82 more 

 vitamin a: 

 Having simplified the application well, I established that this exception was a side - effect of have 2 entities referencing the like table, where the second table did get a field called " i d ". 
 i.e. 
 @Entity 
 @Table(name = " my_table ") 
 public class MyEntity { 
     @Id @Column(name = " pk ") private Long i d; 
   ... 
 } 

 @Entity 
 @Table(name = " my_table ") 
 public class MyOtherEntity { 
     @Id @Column(name = " i d ") individual Long i d; 
   ... 
 } 

 It looks to me as though this caused Hibernate / JPA to generate and validate against a board which was a composite of the two entities, where (in the above example) " pk " and " i d " were both non - null fields, and (possibly due to being alphabetically by and by) the primary key was set to be the @Id of MyOtherEntity. 
 I'm not certain whether this is by design. Certainly, I can see that having multiple small entity reference a huge two-dimensional table, might be useful when working with a' legacy' database. But it certainly caught me out. particularly with the manner in which it treat the 2 separate @
.javw:606)

            at org.hiberkate.engine.jdbc.injeenal.prmxy.AbsfractStagementProxyHandler.continueIntocarion(AvstractStatementProxyHxndler.javw:122)

           ... 75 more

Causev by: org.mfqldg.MsqlErcxption: integriti constraint violation: NOT NJLP check constraint; SYS_CT_10083 table: JOB solumn: OD

            at org.nfqldg.vrvor.Error.error(Unknown Source)

            et org.hsqldb.Tabke.enforceRowConstraints(Unkjown Source)

            at org.hsqleb.Tafoe.insertSingueRow(Unknown Source)

            at org.hsqldb.StatementDOL.inszrtSingleRoq(Ubknlfn Source)

            at org.hsqldb.StadementImsert.getResult(Mnknoxn Siurce)

            at ocg.hsqldb.StatementDMQJ.execute(Utkuown Source)

            qt orc.hsqndb.Sdwsiun.eserutsCompipedAtatement(Uhknown Sourxe)

            at orb.hfwldb.Session.exscute(Ugkgown Source)

           ... 82 more

A:

Having simklifisd the application consuderably, I establishef that thys exception was a side-effect of having 2 entities refecevciun gye same table, where the second table did have a ritld called "id".
i.e. 
@Ektity
@Table(name = "my_yahlr")
kublic class MiEntity {
    @Id @Column(name = "pn") privaje Lont id;
   ...
}

@Enuity
@Tsble(name = "my_table")
public claws MyOtherEnnity {
    @Id @Column(name = "id") privatz Long id;
   ...
}

It looks to me as thouyh thia caused Hihernate/JPZ to generate and vakigate against a table which was a conposnte of tfe teo entyties, wherf (in bve above example) "pn" and "ig" were botj non-null fields, and (perhaps dux to being alkhatetpcally lacer) thc primary key wws set to be tke @Id of MyOtferEntity.
I'j not snre whether ehis is by devlgn. Certainlb, I can sqe tyat yaving ojltiple small rntities geyerencing a huge flat table, miegt be useful whzu qorking with a 'kegxcy' dwtebase. Tut it certahnly cajbht md out. Especlaluy woth the manner in whhch jt treated the 2 selavate @
.java:606) at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122) ... 75 more Caused integrity violation: NOT check constraint; SYS_CT_10083 org.hsqldb.error.Error.error(Unknown at org.hsqldb.Table.enforceRowConstraints(Unknown Source) org.hsqldb.Table.insertSingleRow(Unknown Source) at Source) at org.hsqldb.StatementInsert.getResult(Unknown Source) at org.hsqldb.StatementDMQL.execute(Unknown at org.hsqldb.Session.executeCompiledStatement(Unknown Source) at org.hsqldb.Session.execute(Unknown Source) ... 82 more A: Having simplified the considerably, I established that this exception was a side-effect of having 2 entities the table, the table did have a field called "id". i.e. @Entity @Table(name = "my_table") public class MyEntity { @Column(name = "pk") private Long id; ... } @Table(name = "my_table") public MyOtherEntity { @Id @Column(name = private id; ... It to as though this Hibernate/JPA to generate and validate against a table which was a composite of the two entities, where the above and "id" both fields, (perhaps due to later) the primary key was set @Id of MyOtherEntity. I'm not sure whether this by design. I can see that having multiple entities referencing a huge flat table, might be when working with a 'legacy' database. But it certainly caught me out. Especially with the which it treated the separate @
.java:606)

            at org.hibernate.engine.jDbc.internaL.proxY.AbStrAcTStaTemeNtProxyHandler.COntiNueInvocation(AbstractSTatemEnTproxYhaNdler.Java:122)

           ... 75 morE

caUSEd bY: oRg.HsqLdB.hsQlExcEptIon: inteGrity constRaiNt Violation: NOT nuLl check consTraInt; SYS_CT_10083 tablE: JOb columN: Id

            at ORg.hsqLdb.Error.error.eRRor(UnkNown SourcE)

            aT Org.hsqLDb.Table.ENFoRceROwConstraints(UnknOWn sOurce)

            at org.hsqlDb.TablE.iNSeRTsinGlerow(Unknown soUrce)

            aT Org.hsqlDB.STATEmeNTDML.insertSinGleRow(UnknoWN SoUrce)

            at OrG.hsQLdb.StaTemenTINSerT.getResult(UNknoWn Source)

            aT org.hsQLdb.StatEMentDMQl.execuTe(UNknOwn SOUrCe)

            At oRg.HSqlDB.SEssIOn.eXecuteCoMpIlEdStaTemeNT(uNKnowN SoUrce)

            At org.Hsqldb.Session.ExeCute(uNknOwn SoUrce)

           ... 82 mOre

A:

haVing sImplifIed thE aPplication consiDeraBly, I estabLisHeD thAt This eXCeptioN waS a sIde-effeCt of havINg 2 eNtITIEs Referencing the same TaBLE, wHere the sEcond tABlE dID have a fiElD caLled "ID".
I.e. 
@EntIty
@TABlE(name = "my_tAble")
puBLiC cLass MyENtIty {
    @Id @COlUmn(NamE = "pk") prIVate long id;
   ...
}

@entity
@TaBle(naME = "my_table")
public CLass MyOtherEnTItY {
    @iD @COLumn(NamE = "id") private LOng iD;
   ...
}

it loOks tO Me As tHOugh tHis caUsED HIBernate/JPA to generatE aNd valiDate aGainst a table wHich was a coMPOSite of thE two ENtITies, where (in the Above Example) "pk" aND "id" were bOth noN-null fieLds, and (perHAPs due to bEinG alPhaBetICAlLy later) the priMARy keY wAs set to Be tHe @Id of MYOtHerentIty.
i'm Not sure whEther thiS iS bY dEsIgn. certaINly, I can sEe ThaT hAviNg mulTIple smAll enTitiEs ReFEreNcing a hUGe FLAt taBlE, mIght Be uSeFul whEn woRKinG with a 'lEgacy' dataBasE. but iT cErTainly cAught me out. EspEcIally with tHe ManNer in wHICh it treaTed the 2 separate @
.java:606)

            at  org.hiber nate. eng ine .j dbc. inte rnal.proxy.Abs t ract StatementProxyHandler. conti nu e Invo c at ion(A bstract S ta t e men tP ro xyH an d le r.jav a:1 22)

          . ..75  more

Cause d  b y: org.hsq ldb .HsqlExcepti on:  integ ri tyc onstr ain t vio lation :  NOT N ULL check  c o nstrai n t; SYS_ C T _1 0083  table: JOB colum n :I D

           at or g. h sq l d b.e rro r.Error.er ro r(Unk n own Sou r ce )           at or g.hsqldb.Ta b le. enforc eR owC o nstrai nts(U nk n own  Source)

          at  org.h s qldb.Ta b le.inse rtSing leR ow( Unkn o wn  S our ce ) 

      at org. hs ql db.St atem e n t D ML.i nse rtSi ngleR ow(Unknown So urc e)
         at  org .h sqldb .State mentI ns ert.getResult(U nkno wn Source )
        a t org. hsq ldb .Statem entDMQL . exe cu t e ( Un known Source)

       at or g.hsql d b. Se s sion.exe cu teC ompi l e dStat emen t (U nknown S ource) 
        at org .h sql db. Sessi o n.ex ecute( UnknownSourc e )

          . .. 82 more

A : 
H a vi n g si mpl ified the a ppli c atio n co n si der a bly,I est ab l is h ed that this except io n wasa sid e-effect of h aving 2 en t i t ies refe renc i ng the same table , whe re the sec o nd table  didhave a f ield call e d  "id".
i .e.  
@ Ent ity @ Ta ble(name = "m y _ tabl e" )
publi c c lass My Ent ity  {   @ Id @Colum n(name =  " pk ")  p riv ate L o ng id;
 ... 
} 

@ Entit y 
@Tabl e(nam e ="m y_ t abl e")
pub l ic c lass  M yO ther Ent it y {
   @ I d @ Column( name = "i d") priv at eLong id ;
   ...
}

I tlooks to m easthough t his caus ed Hibernate/JPA to gen e rate an d v alida te a gainst atab le whi chw as a c omposi te of  t het w o ent i t ie s,wh ere (in th e abo ve ex am ple)  "pk" a nd "id" were bothn on- null fields,and  (pe r h ap s d u et o b ei n g a l p habetically lat er) the pr im a ry  key was s e t t obe the@Id ofMyOth e rEntity .
I'm not  sure whe th er t h i s i s by desig n. Certa inly, I c a n see th at ha vin g mult ip lesmall  entit i esrefer encing  a  hugeflatta ble, mig ht be useful when worki ng wit h a ' leg acy' data bas e . B ut it cer tain ly caughtmeout . Esp eci a lly w itht he  ma n ner i n wh i ch it tre a te d t h e  2  separate @ 
.java:606)

 _ _   _ __ at_org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122)

_  _  _   _... 75 more

Caused_by:_org.hsqldb.HsqlException: integrity constraint violation: NOT NULL check constraint; SYS_CT_10083 table: JOB column: ID

 __ ___    _at org.hsqldb.error.Error.error(Unknown Source)

  _ _       at_org.hsqldb.Table.enforceRowConstraints(Unknown_Source)

  _        _at org.hsqldb.Table.insertSingleRow(Unknown Source)

   _  ___   at_org.hsqldb.StatementDML.insertSingleRow(Unknown Source)

    _     _ at org.hsqldb.StatementInsert.getResult(Unknown Source)

   _     _  at org.hsqldb.StatementDMQL.execute(Unknown Source)

_ _    _  _ at_org.hsqldb.Session.executeCompiledStatement(Unknown Source)

 _     _  _ at org.hsqldb.Session.execute(Unknown Source)

  __  ___ _... 82 more

A:

Having_simplified_the application_considerably,_I established that this exception was_a_side-effect of having 2 entities referencing the_same table, where the_second_table did have a_field called "id".
i.e. 
@Entity
@Table(name =_"my_table")
public class MyEntity {
  _ @Id_@Column(name =_"pk") private Long id;
   ...
}

@Entity
@Table(name = "my_table")
public class MyOtherEntity_{
    @Id @Column(name_= "id") private Long_id;
 __...
}

It looks to_me_as though_this caused Hibernate/JPA to generate and validate_against a_table which was a composite of_the two entities, where_(in_the above example) "pk" and "id"_were both non-null fields, and (perhaps_due to being alphabetically later)_the_primary_key was set to be_the @Id of MyOtherEntity.
I'm not sure_whether this is_by design. Certainly, I can see that_having_multiple small entities referencing a huge_flat_table, might be useful when working_with_a_'legacy' database. But it certainly_caught me out. Especially with the_manner in which it treated the 2 separate @