How do I add fields to an existing tuple format when using the Java bindings?
If you are currently storing objects using a TupleBinding, it is possible to add fields to the tuple without converting your existing databases and without creating a data incompatibility. Please note also that class evolution is supported without any application level coding through the Direct Persistence Layer API. This excerpt from the Javadoc may be made to tuple bindings. Collections Overview The tuple binding uses less space and executes faster than the serial binding. But once a tuple is written to a database, the order of fields in the tuple may not be changed and fields may not be deleted. The only type evolution allowed is the addition of fields at the end of the tuple, and this must be explicitly supported by the custom binding implementation. Specifically, if your type changes are limited to adding new fields then you can use the TupleInput.available() method to check whether more fields are available for reading. The available() method is the implementation of java.io.Inpu
Related Questions
- Will phoneME Advanced software be backwards-compatible with the Java technology implementation on existing phones?
- Is it possible to add new fields, or change the types of existing fields (e.g. change "Office Phone" to "Home Fax")?
- New Fields added to the Call List table in Interaction Dialer must be in which format?