[forge-issues] [JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays

[George Gastaldi (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763113#comment-12763113 ] 

George Gastaldi commented on FORGE-835:
---------------------------------------

lob is okay and it's similar to JPA naming standard.

I recall that some DBs (I think Derby is one of them) also needs the size of the @Column annotation to be set to Integer.MAX_VALUE
                
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
>                 Key: FORGE-835
>                 URL: https://issues.jboss.org/browse/FORGE-835
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Builtin Plugins
>    Affects Versions: 1.2.2.Final
>            Reporter: Ivan St. Ivanov
>            Assignee: Ivan St. Ivanov
>             Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> {code:java}
> field lob --named <field-name> 
> {code}
> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira