RE: [Hibernate-devel] SQL Server 2000 questions

[Brad C. <bra...@wo...>]

hi donnie

get the cvs version.  it has an ant build script that enables u to
compile, javadoc, test, etc.

gavin, if hibernate is sticking with the one distribution (classes and
source together) then i think the user should be able change the code
and rebuild the distribution easily.    to achieve this the ant script
should be included and possibly the libs.  if u wanted to tidy this
aspect of the project up using ant as the one build tool, i can
certainly give u a hand.  also, the java source is currently included in
the jar.

on your philosophical topic (and each to his/her own here), i work the
opposite way (even after being a dba somewhere in the dim, dark past).
i find it much more intuitive and less time consuming to work at the
object level, since that is what all my code that implements the
application's logic is directly manipulating.  how those objects are
persisted is then not the most important thing.  having said that, i do
go and check/tweak the schema to ensure integrity and performance.  just
my thoughts, like i said, each to there own.

i agree that writing bean-style property methods is tedious, but it is a
task than can be fairly easily automated.

brad

> -----Original Message-----
> From: Donnie Hale [mailto:do...@ha...]
> Sent: Monday, 15 April 2002 5:13 AM
> To: hib...@li...
> Subject: RE: [Hibernate-devel] SQL Server 2000 questions
>=20
>=20
> Gavin,
>=20
> Thanks for responding.
>=20
> I was able to figure out how to run FooBarTest. After setting=20
> the proper
> "SelectMethod=3Dcursor" parameter in the URL, I was able to run=20
> a large number
> of the tests. Here are a couple of the issues I encountered:
>=20
> In testLoad there was a NPE, though the program kept running:
>=20
> testLoad...
> java.lang.NullPointerException
>         at
> cirrus.hibernate.impl.RelationalDatabaseSession$Key.hashCode(R
> elationalDatab
> aseSession.java:183)
>         at java.util.HashMap.hash(HashMap.java:250)
>         at java.util.HashMap.get(HashMap.java:301)
>         at
> cirrus.hibernate.impl.RelationalDatabaseSession.save(Relationa
> lDatabaseSessi
> on.java:464)
>         at
> cirrus.hibernate.impl.RelationalDatabaseSession.insert(Relatio
> nalDatabaseSes
> sion.java:445)
>         at=20
> cirrus.hibernate.test.FooBarTest.testLoad(FooBarTest.java:178)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39
> )
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl
> .java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at cirrus.hibernate.test.TestCase.run(TestCase.java:46)
>         at cirrus.hibernate.test.FooBarTest.main(FooBarTest.java:1217)
>=20
> In testQuery, there was this exception:
>=20
> testQuery...
> Exception in thread "main" java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.java:39
> )
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl
> .java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at cirrus.hibernate.test.TestCase.run(TestCase.java:46)
>         at cirrus.hibernate.test.FooBarTest.main(FooBarTest.java:1217)
> Caused by: java.lang.Exception: component query
>         at cirrus.hibernate.test.TestCase.assertTrue(TestCase.java:66)
>         at=20
> cirrus.hibernate.test.FooBarTest.testQuery(FooBarTest.java:323)
>         ... 6 more
>=20
> I couldn't quite figure out what was underlying this issue.=20
> You'll note from
> the "... 6 more" line that this was under JDK 1.4. It was=20
> with the 0.9.8
> release.
>=20
> A couple of other comments, most of which you probably know:
>=20
> 1) The sybase dialect really isn't appropriate for SQL Server=20
> 2000. SS2K has
> data types that a lot more directly map to the java.sql.Types=20
> (e.g. bit to
> BIT, bigint to BIGINT, etc.).
>=20
> 2) In trying to workaround one problem, I had to change some=20
> hibernate code
> (nothing permanent). The lack of a build facility meant I had=20
> to cobble


> _______________________________
> brad clow
> chief technical officer
> workingmouse
>=20
> email: bra...@wo...
> web:   http://www.workingmouse.com
>=20