Make sql backend optional #1086
Comments
|
The goal is actually to completely remove the old backend and switch everyone to sql. Do you have any particular reasons not to use the sql backend? |
|
Hm... not many except it is PITA to deal with OpenSSL when cross-compiling for aarch64 on amd64. So even though I did not add SQL backend to our service code, it is still pulled in via dependencies, compiled and caused headache that I would rather not have. This is the first and only dependency pulling OpenSSL in our huge monorepo. |
vedhavyas
added a commit
to autonomys/frontier
that referenced
this issue
Jun 23, 2023
Making SQL optional would be great and does not brings unwanted dependencies when SQL is not used. Here is an example: polkadot-evm#1086
sorpaas
pushed a commit
that referenced
this issue
Jun 26, 2023
Making SQL optional would be great and does not brings unwanted dependencies when SQL is not used. Here is an example: #1086
|
This issue was fixed in #1089 |
|
Nice, thank you! |
vedhavyas
added a commit
to autonomys/frontier
that referenced
this issue
Jun 28, 2023
Making SQL optional would be great and does not brings unwanted dependencies when SQL is not used. Here is an example: polkadot-evm#1086
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe consider making this feature optional? It pulls way too many dependencies, including OpenSSL.
Originally posted by @nazar-pc in #883 (comment)
The text was updated successfully, but these errors were encountered: