othercorey

I can't think of a clean way to do this generically. Users can customize the command to overwrite the options.

Please describe the tables you are trying to bake.

The schemas. You post an error about "unrelated tables" but gave us no information.

> At least beginners experiment a lot, confusion about changed/unchanged files happens. A lot of work can get lost. How will this help work being lost?

@lab-at-nohl You should probably only re-generate files if you never customize them. Only new files should be baked.

I still don't understand how that avoids losing work. If the file is unchanged, what work is lost? Isn't work lost when the file *is* changed?

> The only thing that adding the check would do is avoid having to show message to user asking whether file should be overwritten. Instead bake could just say "The...

Support for updating table and entity classes will be in bake 2.8.

This seems to expect the primary key to be generated. However, for multi-column keys, that's probably not true. Users can work around it by removing the primary key and introducing...

> @othercorey Hi, so your suggestion would be adding both columns to $_accessible for multi-column primary key? Yes. For a complete solution, we should decide if a primary key could...