re-design Statement/ParameterStatement.execute[Query|Update](?sql string)
interfaces
------------------------------------------------------------------------------------
Key: CAROB-81
URL: https://forge.continuent.org/jira/browse/CAROB-81
Project: Carob
Type: Improvement
Components: C++ API
Versions: V1.0 - beta, V1.0 - full version
Reporter: Marc Herbert
Assigned to: Gilles Rayrat
The JDBC interface allows:
1. only execute("...") methods WITH a request argument on Statement objects
2. only execute() methods WITHOUT a request argument on PreparedStatement
objects.
The rationale is that:
- the request argument is not mutable
- for PreparedStatement, it must be defined at construction time in order to
actually be prepared.
See SEQUOIA-383 for more JDBC details.
Carob currently "maps" half of these restrictions on
Statement/ParameterStatement classes.
This is confusing and probably wrong because:
- Carob's ParameterStatements have nothing to do with preparation, only with
parameters.
There is no "prepare" concept in carob (because sequoia does not implement it
anyway).
- only restriction 2. is implemented, 1. is allowed. (which means the request
is mutable in this case!).
This carob API should be much simplified/clarified. Maybe we could keep the
interesting "non-mutable" concept,
but implemented differently.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Carob mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob
