1998-02-24 16:52:13 +01:00
|
|
|
The complete structure definition has to be listed inside the declare
|
1998-05-06 15:03:47 +02:00
|
|
|
section of the structure variable for ecpg to be able to understand it.
|
1998-02-24 16:52:13 +01:00
|
|
|
|
1998-06-03 15:55:15 +02:00
|
|
|
The error message for "no data" in an exec sql insert select from statement
|
|
|
|
has to be 100.
|
|
|
|
|
|
|
|
sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified in a SET
|
|
|
|
DESCRIPTOR statement will be ignored.
|
|
|
|
|
1999-11-22 13:48:48 +01:00
|
|
|
If a NOTICE message is given by the backend it should not be printed to
|
|
|
|
stderr. Instead it should be listed as a warning.
|
|
|
|
|
1999-12-08 10:52:29 +01:00
|
|
|
The error handling has to be improved by adding additional error-rules to
|
|
|
|
the parser.
|
|
|
|
|
2000-02-16 12:52:25 +01:00
|
|
|
it would be nice to be able to use :var[:index] or :var[<integer>] as
|
|
|
|
cvariable for an array var
|
1998-06-03 15:55:15 +02:00
|
|
|
|
1999-10-15 21:02:08 +02:00
|
|
|
What happens to the output variable during read if there was an
|
|
|
|
indicator-error?
|
|
|
|
|
|
|
|
Add a semantic check level, e.g. check if a table really exists.
|
|
|
|
|
2000-02-17 20:48:58 +01:00
|
|
|
It would be nice if there was a alternative library using SPI functions
|
|
|
|
instead of libpq so we can write backend functions using ecpg.
|
|
|
|
|
2000-02-22 20:57:12 +01:00
|
|
|
remove space_or_nl and line_end from pgc.l
|
|
|
|
|
1998-05-21 05:52:37 +02:00
|
|
|
Missing statements:
|
|
|
|
- SQLSTATE
|