Recently I have upgraded my project to Java 11 and postgres to version 12 (flexi server). I have also updated JOOQ to 3.16.2 from 3.12. Since these upgrade code generation is not happening for the new tables created in postgres.
e.g. before the above upgradation for a particular schema let’s say there were 10 tables. And after upgradation I have added 2 new tables. Now code generation is not happening for the 2 newly created tables. For old tables code generation happened successfully.
Please let me know how to fix this issue. I have also tried with JOOQ version 3.14.15. But no luck
Related
I published my app on play store and I have made an update that may cause the older one to crash due to some database structure changes that I have made and I have had a hell of hustle trying to automate DB migration upon installation. So I want the to completely auto-uninstall the old one from users phone before new one is installed during update as an easy solution. Is there a way I can include such configurations?
No, there is no way to force uninstallation before installation. But it sounds like you could just delete your DB on upgrade using SQLiteOpenHelper
If you use GreenDAO
you can use the schema version
Schema schema = new Schema(, "greendao");
when increasing the schema version GreenDAO will empty your DB and update the schema, and then you can repopulate it from the server (if applicable)
We have just upgraded our database from SQL Server Express to SQL Server 2014 Web Edition.
We are also, and don't ask me why, using Subsonic as our database provider.
As soon as we pointed our code to the new SQL 2014 edition we got errors.
It seems that Subsonic has decided, on some queries that involve paging, to drop Where clauses so that the following And clause causes an error.
Has anyone else experienced any issues with Subsonic and SQL Server 2014 Web Edition.
We are using Subsonic 2.2 and are hesitant to upgrade to 3 unless we know it'll work as this is a major piece of work.
Note
The code works fine with SQL Server 2012 Business edition.
As noted in the comments you need to update the source code for Subsonic.
This is within ..\SubSonic-2.0-master\SubSonic\DataProviders\DataService.cs when you get the code from GitHub.
The area to update is below. Depending how you want to update it but for me using SQL Server 2012 I have just defaulted to Sql2008Generator :-
case DataProviderTypeName.SQL_SERVER:
if(Utility.IsSql2005(provider))
generator = new Sql2005Generator(sqlQuery);
else if(Utility.IsSql2008(provider))
generator = new Sql2008Generator(sqlQuery);
else
generator = new Sql2000Generator(sqlQuery);
break;
I have an app in appstore and in which I had setup my magicalrecord using setupCoreDataStack method. I have since then versioned the data model and added an attribute to an existing entity. Now when I use setupCoreDataStackWithAutoMigratingSqliteStoreNamed to perform lightweight migration over the released app, the debug app opens with no data.
The new version of data model is currently selected with the green tickmark in xcode and is based on the old data model. The default value for the new attribute is set. If I install released version again without deleting the debug app from the device then I see the old data, means the old data is never wiped off (which is good), it's just not shown after setting up new version of the model and performing magicalrecord lightweight migration. What am I missing here?
There is no error in debugger while loading new debug version over existing released version. The filemerge diff performed on the contents of the data model versions only show the addition of the new attribute.
Any insight into this problem or pointers will help!
Huh, read somewhere that you can't auto-migrate if the datastore was not setup as an auto-migrate store in the first place. Someone suggested doing it over multiple releases. So assuming that was true, I tried
[MagicalRecord setupAutoMigratingCoreDataStack];
right before
[MagicalRecord setupCoreDataStackWithAutoMigratingSqliteStoreNamed:#"XYZ"];
and it worked.
Anyone else with same problem, no need to delete data store and create new with setupAutoMigratingCoreDataStack or try manual migration. Just setup as auto-migrate store and do auto-migration one after another in the same build. Hope it works for your too!
I've been running usergrid-stack commit 08f26cc865c96185d11990bf622730beff59971a for a while using the built-in cassandra db.
I need to migrate to another server and thought I'd take the chance to update.
I tried copying the folder standalone/target/tmp to the new installation but doing so gives me the error below.
null; Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=hinted_handoff_throttle_delay_in_ms for JavaBean=org.apache.cassandra.config.Config#6b7b9f29; Unable to find property 'hinted_handoff_throttle_delay_in_ms' on class: org.apache.cassandra.config.Config
Invalid yaml; unable to start server. See log for stacktrace.
Is there any way to migrate the db to a newer version?
If not, is there at least a way to migrate the db using the old version?
iirc hinted_handoff_throttle_delay_in_ms is a setting from Cassandra 1.1 which was removed in Cassandra 1.2 so you might need to edit the conf file (cassandra.yaml) and remove this setting.
Does Subsonic work with Advantage Database server and if so are there any TT files to generate the necessary code
From the docs:
Subsonic 2.2 Currently supports 5 main database engines:
SQL Server (2000 through 2008)
MySQL (5.0+) with special support for InnoDB
Oracle - although we've had reports of some issues with Foreign Keys and Stored Procedures
SQL CE (Compact Edition)
SQLite
SubSonic 3.0 supports and has templates for:
SQL Server (2000-2008)
MySQL (5.0 +)
SQLite
Oracle support is currently in development - you can get the latest version of the templates from github. Please post details of any issues or questions to the SubSonic google group.
So in short unfortunately the answer is no.