You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Chad Schoettger (JIRA)" <ji...@apache.org> on 2007/04/07 03:55:32 UTC
[jira] Commented: (BEEHIVE-1189) JDBC Control batch updates with
bean parameters cause compilation error
[ https://issues.apache.org/jira/browse/BEEHIVE-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487373 ]
Chad Schoettger commented on BEEHIVE-1189:
------------------------------------------
Statement should be:
@SQL(statement="INSERT INTO ( {customer.fname}, {customer.id}", batchUpdate=true)
public int[] doBatchUpdate(Customer c);
> JDBC Control batch updates with bean parameters cause compilation error
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-1189
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1189
> Project: Beehive
> Issue Type: Bug
> Components: System Controls
> Affects Versions: V1Alpha, V1Beta, v1m1, 1.0, 1.0.1, 1.0.2
> Reporter: Chad Schoettger
> Assigned To: Chad Schoettger
>
> If a JDBC control declares a method which uses bean parameters, the JDBC fails to compile due to an error in the JDBC system control APT checker.
> For example:
> @SQL(statement="INSERT INTO ( {customer.fname}, {customer.id})
> public int[] doBatchUpdate(Customer c);
> The following apt error is generated:
> rg.apache.beehive.controls.api.ControlException: Illegal argument in SQL statement: cust.fname; unable to find suitable method
> of retrieving property fname out of object cust.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.