[Hibernate-JIRA] Created: (HHH-3465) HiRDB Support
by Tomoto Shimizu Washio (JIRA)
HiRDB Support
-------------
Key: HHH-3465
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3465
Project: Hibernate3
Issue Type: New Feature
Components: core
Affects Versions: 3.2.5
Environment: 3.2.5 + HiRDB V8 + Type4 JDBC Driver
Reporter: Tomoto Shimizu Washio
Attachments: hirdbdialect.patch
I would like to contribute with a dialect for HiRDB, Hitachi's RDBMS.
(For more information, please see http://www.hitachi.co.jp/Prod/comp/soft1/global/prod/hirdb/)
I added 4 classes and slightly modified 2 existing classes as shown below. Please look at the documentation at the top of the patch for explanations.
org.hibernate.dialect.HiRDBDialect (added)
org.hibernate.dialect.UserFuncDeclParser (added)
org.hibernate.dialect.DialectFactory (modified)
org.hibernate.dialect.function.AnsiTrimEmulationFunction (modified)
org.hibernate.dialect.function.AnsiTrimEmulationFunctionWithTrimstrs (added)
org.hibernate.dialect.function.TypeQualifiedSQLFunction (added)
You may think this code is relatively large as a dialect. It is because I also implemented user-defined function support. As HiRDB requires '?' parameters to be qualified by 'as <type>' in user-defined function invocations, I made a parser for the type declarations that the user specified in the properties file, and a renderer for the type qualifier. See javadoc comments of HiRDBDialect and UserFuncDeclParser for more details.
This patch is created on Hibernate 3.2.5.ga and tested on HiRDB V8 with Type4 JDBC Driver. The example configuration for HiRDB is shown below:
hibernate.dialect org.hibernate.dialect.HiRDBDialect
hibernate.connection.driver_class JP.co.Hitachi.soft.HiRDB.JDBC.HiRDBDriver
hibernate.connection.url jdbc:hitachi:hirdb://DBID=@HIRDBENVGRP=C:/hirdb.ini
hibernate.connection.username hitachi
hibernate.connection.password hitachi
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[Hibernate-JIRA] Created: (HHH-5554) Customise column aliasing scheme
by Chris Pheby (JIRA)
Customise column aliasing scheme
--------------------------------
Key: HHH-5554
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5554
Project: Hibernate Core
Issue Type: Patch
Components: core
Affects Versions: 3.6.0.Beta4
Reporter: Chris Pheby
Attachments: alias-patch.patch
Currently, the column aliasing scheme is hardcoded in the method public String getAlias(Dialect dialect) of the Column class. Essentially, this constructs an alias by creating a prefix using any characters up to the first non-letter character in the column name. This is usually followed by '_' and a number for disambiguation.
I am working with a legacy database where many columns share common prefixes such as 'CUS_', 'COL_'. These mean all the aliases end up being the same for many columns, making queries difficult to debug.
This patch configures aliasing via Dialect, which was already being done for getMaxAliasLength(). This makes it possible to customise the behaviour by extending the Dialect being used. It does not otherwise change the standard behaviour.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[Hibernate-JIRA] Created: (HV-589) Consider keeping a constant placeholder instead of the full memory model for classes not indexed
by Emmanuel Bernard (JIRA)
Consider keeping a constant placeholder instead of the full memory model for classes not indexed
------------------------------------------------------------------------------------------------
Key: HV-589
URL: https://hibernate.onjira.com/browse/HV-589
Project: Hibernate Validator
Issue Type: Improvement
Components: engine
Affects Versions: 4.3.0.Final
Reporter: Emmanuel Bernard
Andrej Golovnin wrote:
> After updating JBoss 7 to use the Hibernate Validator 4.3.0 and
> adding <property name="javax.persistence.validation.mode" value="NONE"/>
> to our persistence.xml file I was able to reduce memory consumption
> of SerializableValidatorFactory from ca. 90MB to ca. 256KB. :-)
> What I was not able to do, is to avoid loading of Hibernate Validator
> and Hibernate Envers at all as we don't use them.
Emmanuel's reply
If you do not use Hibernate Validator annotations, 90MB might indeed be too much :) Hardy, I wonder if we could optimize the memory model and JPA initialization so that we check if a class has constraints and if it does not, Hibernate Validator keeps a small placeholder to remember that but does not consume any other memory for this non validated class. We could save a lot instead of building the model and keeping it in memory.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months