You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something bad with my build. imapsql: using transpiled SQLite (modernc.org/sqlite), this is experimental imapsql: NewBackend (initSchema): create table users: SQL logic error: AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY (1)
build from master
Steps to reproduce
Build with GOOS=linux GOARCH=arm64 ./build.sh --static`
I figured out that this db-hack doesn't work on my deployment.
I didn't find how to force maddy to run that hack on init db. Also I didn't find how to force maddy to use sqlite3 driver. I think that modernc.org/sqlite also requires dbhack run?
@foxcpp not related directly to the issue, but I noticed in linked code that you have strings.HasPrefix(res, "ALERT TABLE"). I don't know of the ALERT statement in any DBMSes, maybe you mistaken for ALTER?
Describe the bug
Something bad with my build.
imapsql: using transpiled SQLite (modernc.org/sqlite), this is experimental imapsql: NewBackend (initSchema): create table users: SQL logic error: AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY (1)
build from master
Steps to reproduce
Log files
go env
GOOS=linux GOARCH=arm64 ./build.sh
maddy.log
Configuration file
/etc/maddy/maddy.conf
Environment information
The text was updated successfully, but these errors were encountered: