Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>So I'm thinking of switching to EnumType.STRING to not have to remap ordinal values in the database again. But if I do this, then how do I sort properly? The alphabetical order of the enum strings is not the order I need.</p> </blockquote> <p>I personally totally avoid using the evil <code>EnumType.ORDINAL</code> as just changing the order of the constants would brake the persistence logic. Evil. That said, <code>EnumType.STRING</code> is indeed not always appropriate. </p> <p>In your case, here is what I would do (with standard JPA): I would persist an <code>int</code> at the entity level and perform the enum conversion in getter/setters. Something like this. First, the enum:</p> <pre><code>public enum Status { PLANNING("Planning", 100), DEVELOPMENT("Development", 200), PRODUCTION("Production", 300); private final String label; private final int code; private Status(String label, int code) { this.label = label; this.code = code; } public int getCode() { return this.code; } private static final Map&lt;Integer,Status&gt; map; static { map = new HashMap&lt;Integer,Status&gt;(); for (Status v : Status.values()) { map.put(v.code, v); } } public static Status parse(int i) { return map.get(i); } } </code></pre> <p>So basically, the idea is to be able to get a <code>Status</code> by its <code>code</code>. And we keep some room between constants so that adding values is possible (it's not pretty but, well, it will work and should be safe for some time). </p> <p>And then in the entity:</p> <pre><code>@Entity public class Project { private Long id; private int statusCode; @Id @GeneratedValue public Long getId() { return this.id; } private void setId(Long id) { this.id = id; } @Transient public Status getStatus () { return Status.parse(this.statusCode); } public void setStatus(Status status) { this.statusCode = status.getCode(); } protected int getStatusCode() { return statusCode; } protected void setStatusCode(int statusCode) { this.statusCode = statusCode; } } </code></pre> <p>The getter/setter for the <code>int</code> representation are protected. The public getter/setter deal with the conversion.</p> <p>An alternative solution would be to use a custom type (at the cost of portability).</p> <h3>Related questions</h3> <ul> <li><a href="https://stackoverflow.com/questions/352586/how-to-use-enums-with-jpa">How to use enums with JPA</a> </li> <li><a href="https://stackoverflow.com/questions/2751733/map-enum-in-jpa-with-fixed-values">Map enum in JPA with fixed values ?</a> </li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POControl sort order of Hibernate EnumType.STRING properties
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPascal Thivent
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POControl sort order of Hibernate EnumType.STRING properties
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Pascal: Very nice, this is just the kind of solution I was hoping for. My problem seemed like the kind of thing that would require a bit of a hack, and your "hack" seems as elegant as possible. I'll give it a try. Thanks!
      singulars
      1. PO
      1. USTauren
    2. CO@Pascal: Works perfectly! Of course, I had to change my queries to reference the property `statusCode` with values like `Status.PLANNING.getCode()` instead of `status` and `Status.PLANNING`.
      singulars
      1. PO
      1. USTauren
    3. COWhy is `EnumType.ORDINAL` evil? It's small, it's fast. Ok, you (really) shouldn't change the order in the enum declaration, but a comment in the file would do it. `EnumType.STRING` has the same flaw, you can't change the names of the enums. Both approaches have their problems.
      singulars
      1. PO
      1. USwhiskeysierra
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload