Gray
Sorry for the delay on this. Did you come up with a generic solution? We are getting ready to [finally] push 4.49 and I'd like to see if we can...
Welcome @RichardForsey89 . I don't quite understand what you are saying. Are you saying that the SQL generated doesn't add in some SQLite specific `Foreign Key` tag? ORMLite's SQL generation...
Supporting perfect schema generation on all of the supported database types is hard. Right now its doesn't setup foreign key constraints unfortunately. I would recommend adding them afterwards by hand....
The short answer is that you can't without a lot of customization. Unfortunately, ORMLite right now does not support composite objects like this.
Any update on this?
Sorry for the delay @spyhunter99 . The log4j dependencies should be marked as optional so it won't be used unless you provide it. Is that not what you are seeing?
Did you try regenerating the database config file? The config file certainly holds the name of the class in it but if you refactor the class you should just regenerate...
Here's the documentation about how to run and regenerate the database table config file. http://ormlite.com/docs/table-config
Thanks for this. How is backwards compatibility achieved? Does this force ORMLite to Java 8?
Thanks. Good stuff. If you don't mind, please minimize incidental line changes. I see changes to imports to use .* but my eclipse settings will expand that again so please...