courseorchestra / 2bass Goto Github PK

suggested foreign key instruction: /BASS IRRELEVANT VALUE IS {value}/

sets ERRONEOUS VALUES to {value}. All updated values are put to log along with key field values

suggested index instruction: /*DB AKA {comma delimieted names}*/

if 2bass sees that index with AKA name exists, then it considers it OK and doesn't make any changes to db

this enables us to use live index rebuilding in PostgreSQL, when we create the same index with new name and then drop the previous one

suggested instruction:
/* BASS CONTENTS {table name} [DELIMITER COMMA | TAB | COLON | SEMICOLON | 'USER DELIMITER' ] UPDATE METHOD [REPLACE | UPDATE] [KEEP TRIGGERS [ALL | FOR MATERIALIZED VIEWS | selected trigger] ENABLED] [VERSION {version number}

FILENAME |

INLINE CONTENTS
field1, field2
field1, field2

*/

The idea is to keep checksum for every defined table contents. If checksum (or version) has changed then the contents of table is updated.

Replace method assumes truncating table and inserting new values. Update methods assume inserting new, deleting excess, updating changed.

Operation assumes that indexed and triggers are turned off, but we can explicitly say to leave triggers on. It is necessary, for example, for materialized views.

Indempotent approach may seem resource consuming. But putting table contents to vcs is useful in a limited number of cases. And in most of this cases we need modest tables. That would be good alternative for option field, for example.

Suggested bass field instruction: /BASS NULL IS {value}/

unlike DEFAULT it doesn't set field DEFAULT property, just sets value if field value is null. IF field's property NOT NULL is set then the instruction is ignored.