-
Notifications
You must be signed in to change notification settings - Fork 13
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.
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
SQL Preproc issue tracker #371
Comments
I report here some issues I found with the gixsql test suite:
is emitted a lot of time. For instance with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The starting point for this should be #370. And using OCamlPro Gixsql fork : https://github.com/OCamlPro/gixsql
Preproc file generation issues
cobol_indent
when there is a tabulation as a first character : TSQL009A TSQL042AThis causes errors when computing the variable prefix of statements
Group variable
TAB00-REC
is passed as is toGIXSQLSetSQLParams
where it should be the 3 elementary varsCID
,FLD01
andFLD02
.The test fails because the length attribute a variable-length variable should be negative, this is easily done when the variable is defined as
01 v SQL TYPE VARCHAR(100).
but it can be the case from normal COBOL variable.is_varying_len
method by adding support toCOMP-5
to usageINCLUDE
d parts of the working-storage should be accessible to (at least) theSql_typeck
module: TSQL0042AThe absence of the copy file in the compilation unit cause the typeck to return an unknown type/length/flags for all variable originating from such a file, but those value are passed to
GIXSQLSetSQLParams
.Grammar issues
--cobol85
is remove, a grammar error appears in test TSQL018B : apparentlyLOREM IPSUM
is a validEXEC SQL
bloc...Parser issues
VARYING
keyword not supported : TSQL022 NB the test depends on preprocess file contentEXEC SQL IGNORE
block should be handle by another preproc, (the default cobol one ?) as the token inside are to be copied as is in the generated file (I hacked a safeguard to avoid parsing such blocks) (TSQL011A)The text was updated successfully, but these errors were encountered: