Before we can get started with adding another table controller, we have to deal with modifications to our database schema.
The default code for Azure Mobile Apps will deploy the configured schema only if the database is empty.
The scripts to do so are reusable, just swap out your models for the ones within. I don't know why I even asked that because we all know the answer. ..the little things that are no brainers and yet simultaneously timesinks.
The code for this repository can be found here: https://github.com/jcolemorrison/strongloop-automigration-demo Yes. I'd say the only two reasons it's not more ubiquitous is due to two reasons: 1) Pretty Terrible Documentation 2) Geared Towards Creating APIs, not necessarily with Front Ends 3) Terrible Documentation The first one is a usual suspect for most frameworks and is generally the bane of most great dev tools out there.
If the database is not empty, you have to do extra work.
This extra work involves updating the schema of your database. The first we will consider is Code First Migrations. With database first, we adjust the database schema manually, then write C# models to reflect that change.
Your dependencies look OK, can you please double-check things (do @roji unfortunately I still can't scaffold database I am trying do it in VS2015 vlass 4.5.1 project.
The great thing about this is that (like most of Active Record’s functionality) it is database independent: you don’t need to worry about the precise syntax of which Active Record populates automatically will also be added.
Reversing this migration is as simple as dropping the table. You can also use them to fix bad data in the database or populate new fields: method.
The reason I felt it necessary to include the first few parts is that I personally can't stand it when a guide/tip/tutorial just starts in and assumes everything is already set up.
If you're just here to learn about Database Migrations, you can skip to that part of the guide. After doing many many many projects in base Express JS, it is massively refreshing to not have to a) dig through npm package soup kitchen b) ID packages that are well maintained c) connect packages in own home soup d) maintain / customize packages e) reinvent the wheel Does strongloop loopback solve everything? However, spinning up solid REST APIs, dealing with authentication/authorization, having MULTIPLE datasources (one model to mongo one to sql), routing, docs...