Merge look at ON Conflict

[visch]

    > generate_insert_statment

@BuzzCutNorman The API is a WIP, and generate_insert_statement is currently expected to return an insert statement as a string. I have not surveyed different databases for upsert methods, but I think most should be able to extent the basic INSERT INTO <table> (<columns...>) VALUES (...) with something like ON CONFLICT (<pk...>) DO UPDATE SET .... So, the overriding pattern could look something like:

def generate_insert_statement(
    self,
    full_table_name: str,
    schema: dict,
):
    stmt = super().generate_insert_statement(full_table_name, schema)
    stmt += "ON CONFLICT ...`

Wdyt?

Originally posted by @edgarrmondragon in #9 (comment)

[visch]

https://docs.sqlalchemy.org/en/14/dialects/postgresql.html#insert-on-conflict-upsert from @DanNorman :D

[visch]

#9 (comment)

[visch]

This is one piece of #64

[visch]

Decided against this as key constraints could change, I think an upsert as we're doing it makes life a bit simpler than relying on constraints being set properly (Maybe I'm wrong?)

[visch]

Solved with #138