← Back to context Comment by graealex 9 months ago Wait until you hear about ORMs. 3 comments graealex Reply 999900000999 9 months ago I still have to create tables. I still have to migrate tables, these are all things I don't need to worry about with firebase.It all depends on what you need to actually do. The only real weakness of Firebase is the Google lock in. SchemaLoad 9 months ago You still have to worry about data migrations without a schema though. Unless you just never access old records. 999900000999 9 months ago Depends.Let's say you have an object called box.It has 3 properties, the id, it's name and it's weight.4 months later you add a 4th property. Cost, odd records that don't have a cost just return null for that field.
999900000999 9 months ago I still have to create tables. I still have to migrate tables, these are all things I don't need to worry about with firebase.It all depends on what you need to actually do. The only real weakness of Firebase is the Google lock in. SchemaLoad 9 months ago You still have to worry about data migrations without a schema though. Unless you just never access old records. 999900000999 9 months ago Depends.Let's say you have an object called box.It has 3 properties, the id, it's name and it's weight.4 months later you add a 4th property. Cost, odd records that don't have a cost just return null for that field.
SchemaLoad 9 months ago You still have to worry about data migrations without a schema though. Unless you just never access old records. 999900000999 9 months ago Depends.Let's say you have an object called box.It has 3 properties, the id, it's name and it's weight.4 months later you add a 4th property. Cost, odd records that don't have a cost just return null for that field.
999900000999 9 months ago Depends.Let's say you have an object called box.It has 3 properties, the id, it's name and it's weight.4 months later you add a 4th property. Cost, odd records that don't have a cost just return null for that field.
I still have to create tables. I still have to migrate tables, these are all things I don't need to worry about with firebase.
It all depends on what you need to actually do. The only real weakness of Firebase is the Google lock in.
You still have to worry about data migrations without a schema though. Unless you just never access old records.
Depends.
Let's say you have an object called box.
It has 3 properties, the id, it's name and it's weight.
4 months later you add a 4th property. Cost, odd records that don't have a cost just return null for that field.