Dsync generated code does not work with MySQL #46
Comments
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
May 22, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
longsleep
added a commit
to longsleep-io/dsync
that referenced
this issue
Aug 31, 2023
In certain cases it might be not desireable to write CRUD functions by hand. To avoid conflict this change adds the option to skip generating those functions. This for example is a workaround for MySQL which currently is not supported by the generated functions or to support unsigned integers in id fields. Related: Wulf#46 Related: Wulf#47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The generated code from dsync (for
createandupdate) usesget_resultwhich implicitly adds aRETURNINGto the generated SQL statement. MySQL does not supportRETURNINGhence, the trait check for generated code fails as theMysqlConnectiondoes not implement theSupportsReturningClausemarker trait.Instead the
createandupdatefunctions should useexecuteand leave it to the caller if it is needed to actually load the data after insert or update.The text was updated successfully, but these errors were encountered: