Re: [Hibernate-devel] Obstacles creating a new dialect.

[Phillip B. <phi...@cl...>]

Gavin_King/Cirrus%CI...@ci... wrote:

>The hardcoded value is a default. You can specify your own table/column
>name for the HiLoGenerator. But, of course, the table generation tool
>doesn't know about any others. What we would really want is for Datastore
>to have a list of all the HiLoGenerators that were created while reading in
>the mapping. I hadn't got up to this yet.
>
>(1) could you please put it in as a feature request
>(2) any volunteers?
>
I've submitted both this and support for schemas as feature requests. 
 In my battle with SF I seem to have submitted a duplicate of schema 
support - maybe some kind project admin could kill one of them for me?

>That's not such a bad solution. A better one might be if we have some
>schema="" attribute everywhere table="" appears and then have
>getQualifiedTableName() as well as getTableName() on things.... its more
>work though.....your suggestion is probably cool for now.
>
I like your idea of adding the schema attribute, that's why I've added 
it as a feature request.

>
>Just a guess ..... It kind of *looks* like this bug has to do with reusing
>prepared statements for this JDBC driver. Hibernate keeps any prepared
>statements it uses in a cache on RelationalDatabaseSession. You could
>disable this cache by defacing
>RelationalDatabaseSession.getPreparedStatement() and see if the error still
>occurs. If it doesn't, perhaps some System property to disable cacheing is
>in order....
>
Haven't had enough time to look at this yet but I suspect you're right.

Thanks for the help.

Phillip B.