batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BATCHEE-25) entity StepExecutionEntity use reserved names as attributes
Date Tue, 01 Apr 2014 10:36:15 GMT

    [ https://issues.apache.org/jira/browse/BATCHEE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956362#comment-13956362
] 

Hudson commented on BATCHEE-25:
-------------------------------

SUCCESS: Integrated in batchee #512 (See [https://builds.apache.org/job/batchee/512/])
BATCHEE-25 write column names in lower case (struberg: rev 5012f767623c3127f48e68240980be5cbb206d80)
* jbatch/src/main/java/org/apache/batchee/container/services/persistence/jpa/domain/StepExecutionEntity.java
* jbatch/src/main/java/org/apache/batchee/container/services/persistence/jdbc/Dictionary.java


> entity StepExecutionEntity use reserved names as attributes
> -----------------------------------------------------------
>
>                 Key: BATCHEE-25
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-25
>             Project: BatchEE
>          Issue Type: Bug
>          Components: jbatch-core
>    Affects Versions: 0.1-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 0.1-incubating
>
>
> the entity StepExecutionEntity has fields like 'commit', 'rollback', 'write' and 'filter'
which are reserved words in some databases.
> Even if OpenJPA detects this in the respective DBDictionary and renames the fields in
the DB we should just not use reserved words. The main reason is that this renaming is highly
vendor specific and another JPA provider would probably use different column names



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message