Setting initial state/pushing updates of lookup tables to production


#1

We need a way to seed the initial state of lookup tables, and to update these tables during migrations from development to production.

Here’s my proposal:

Sound off below.


#2

Great content! Will you release the 0.10.2 version on github ? If I have some questions, where should I post them? I did post one at community.filemaker.com but never receive any answer…


#3

There’s a few more things I need to add/fix before I release the next build, but it’s going to be soon.

Please use this forum for Karbon-related communication. I’m trying to get this community off the ground and it has to start somewhere.


#4

OK!
So there should be one initializing script per lookup and setting table and then a master script to run all those scripts?
Could you list all those Karbon tables?

Will the rule be to have UUID as primary keys in every table except the lookup and setting tables that will have serial primary keys?


#5

Yes

Could you list all those Karbon tables?

Not sure I understand. You can see a list of the tables in manage database.

Will the rule be to have UUID as primary keys in every table except the lookup and setting tables that will have serial primary keys?

Yes.