The old schema had STAT_DATA be a BLOB, and Depot currently defaults to varbinary(255). This raises at least two questions; first, does it make sense to assume that in the absence of any other markup, 255 is a reasonable size limit? I am not at all sure. Second, whatever the default translation of byte[] ends of being, how to we deal dialect-agnostically with schema compatibility issues?
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@390 c613c5cb-e716-0410-b11b-feb51c14d237
This commit is contained in:
@@ -66,8 +66,11 @@ public class StatRecord extends PersistentRecord
|
|||||||
@Column(name="STAT_CODE")
|
@Column(name="STAT_CODE")
|
||||||
public int statCode;
|
public int statCode;
|
||||||
|
|
||||||
/** The data associated with the stat. */
|
/**
|
||||||
@Column(name="STAT_DATA")
|
* The data associated with the stat. TODO: BLOB will break on PostgreSQL, which in turn
|
||||||
|
* will serve as an excellent TODO reminder that we need to figure out how to deal properly.
|
||||||
|
*/
|
||||||
|
@Column(name="STAT_DATA", type="BLOB")
|
||||||
public byte[] statData;
|
public byte[] statData;
|
||||||
|
|
||||||
/**
|
/**
|
||||||
|
|||||||
Reference in New Issue
Block a user