metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METAMODEL-6) Get back update status after invoking executeUpdate(...)
Date Fri, 11 Dec 2015 08:43:11 GMT

    [ https://issues.apache.org/jira/browse/METAMODEL-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052416#comment-15052416
] 

ASF GitHub Bot commented on METAMODEL-6:
----------------------------------------

Github user LosD commented on the pull request:

    https://github.com/apache/metamodel/pull/77#issuecomment-163876153
  
    Hehe, I'm all for nuking Java7 support, but I do think nulls are the perfect unknown/unavailable
variable... Essentially, that's what they are for.
    
    However, those are general observations, I'm in transit right now, so I can't really check
code. 
    



> Get back update status after invoking executeUpdate(...)
> --------------------------------------------------------
>
>                 Key: METAMODEL-6
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-6
>             Project: Apache MetaModel
>          Issue Type: Wish
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>            Priority: Minor
>
> In the current API design of MetaModel, the DataContext.executeUpdate(...) method is
a void method. This was initially chosen because not all implementations have the capability
to report anything about a particular update. But some do, for instance the no. of inserted,
updated or deleted records from a JDBC call. It would be nice to expose this information when
available.
> My suggestion for this would be to let the DataContext.executeUpdate(...) method return
an object with this information. All methods on the new object type would be optionally returning
null, if no information is available. But when available, we can at least expose it this way.
> The change wouldn't have a major impact, since any project using MetaModel would already
need to recompile because of the namespace change to org.apache.metamodel. And the change
would be compile-time compatible with having a void return type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message