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
-- Test mapping of various SQL column types and properties to C++ types.CREATETABLEIF NOT EXISTS ColumnTypeTest1 (
-- primary keys
integerAutoincrementPK INTEGERNOT NULLPRIMARY KEY AUTOINCREMENT,
-- nullability
integerNotNull INTEGERNOT NULL,
integerNull INTEGERNULL,
-- various column types
tinyIntColumn TINYINT NULL,
smallIntColumn SMALLINTNULL,
integerColumn INTEGERNULL,
bigIntColumn BIGINTNULL,
numericColumn NUMERIC(10, 2) NULL,
booleanColumn BOOLEANNULL,
dateColumn DATENULL,
timestampColumn TIMESTAMPNULL,
datetimeColumn DATETIME NULL,
charColumn CHAR(8) NULL,
varcharColumn VARCHAR(30) NULL,
textColumn TEXTNULL,
blobColumn BLOB NULL,
binaryColumn BINARY(16) NULL,
varBinaryColumn VARBINARY(16) NULL,
-- Unicode column types
nCharColumn NCHAR(8) NULL,
nVarCharColumn NVARCHAR(30) NULL,
nTextColumn NTEXT NULL
);
CREATETABLEIF NOT EXISTS ColumnTypeTest2 (
-- primary keys
guidPK GUID NOT NULLPRIMARY KEY
);
CREATETABLEIF NOT EXISTS ColumnTypeTest3 (
-- primary keys
varcharPK VARCHAR(30) NOT NULLPRIMARY KEY
);
@Yaraslaut but now I realize that this is not quite working in the way we're currently doing the tests, because this is SQL dialect dependant, and thus, we cannot run that test on every database, but only on hard-coded SQLite (as done right now).
Some column names and properties may however differ, depending on the dialect. Would it make sense to move the actual logic of ddl2cpp into the core library and then ahve a way to run the tests in C++, using the migration query builder API? 🤔
The text was updated successfully, but these errors were encountered:
This is the file i had in mind:
@Yaraslaut but now I realize that this is not quite working in the way we're currently doing the tests, because this is SQL dialect dependant, and thus, we cannot run that test on every database, but only on hard-coded SQLite (as done right now).
Some column names and properties may however differ, depending on the dialect. Would it make sense to move the actual logic of ddl2cpp into the core library and then ahve a way to run the tests in C++, using the migration query builder API? 🤔
The text was updated successfully, but these errors were encountered: