Skip to content

docs(schema): note version may be a composite multi-binary toolchain string #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kuzdogan wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs(schema): note version may be a composite multi-binary toolchain string #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion migrations/20250717103432_database.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,11 @@ CREATE TABLE compiled_contracts
the syntax ('solidity', 'vyper', 'yul'). there may be future compilers which aren't solc
but can still compile solidity, which is why we need to differentiate the two

the version should uniquely identify the compiler
the version should uniquely identify the compiler. for single-binary compilers this is
the plain compiler version (e.g. solc '0.8.26+commit.8a97fa7a', vyper 'v0.3.10'). for
toolchains built from multiple binaries it may be a composite string that identifies the
whole toolchain — e.g. zksync's zksolc drives a separate solc backend, and is recorded as
'zksolc:<zksolcVersion>;solc:<solcVersion>' (e.g. 'zksolc:1.5.10;solc:0.8.26-1.0.2')
*/
compiler VARCHAR NOT NULL,
version VARCHAR NOT NULL,
Expand Down
Loading