I'm trying to solve this problem. I was wondering if it's possible to use ORMLite (or modify it) to support this use case ?
Thanks.
I'm trying to solve this problem. I was wondering if it's possible to use ORMLite (or modify it) to support this use case ?
Thanks.
Now, you could create a table of screens which could then have a field table with the name of the screen-id, field name, and other information. You could have a user-id in the screen table so each user could have an entry which corresponds to a list of fields.
public class Screen {
String user;
...
}
public class Field {
Screen screen;
String fieldName;
int fieldPosition;
...
}
But unless you actually need SQL functionality, you may want to consider a different persistence strategy like @mgv mentioned.