Actually I am finding a lot of references online that calling Oracle
procs/functions that define PL/SQL BOOLEAN arguments/returns cannot be done
via CallableStatement. This is going to take some investigation.
On Fri, Sep 30, 2016 at 7:10 PM Steve Ebersole wrote:
> Specifically, does anyone kno
Specifically, does anyone know how Oracle driver
reports ParameterMetaData#getParameterType for CallableStatement arguments
that are defined as PL/SQL BOOLEAN types?
On Fri, Sep 30, 2016 at 7:02 PM Steve Ebersole wrote:
> We may be able to look at the procedures Metadata from CallableStatement.
We may be able to look at the procedures Metadata from CallableStatement.
I forget the exact details of how it reports the argument types, especially
for Oracle specifcally
On Fri, Sep 30, 2016, 12:57 PM Vlad Mihalcea
wrote:
> I also consider that we should provide info so that we can properly m
I also consider that we should provide info so that we can properly map the
Boolean type according to the expected SQL type.
Especially since we have revamped the support for Stored procedures and
functions.
Vlad
On Fri, Sep 30, 2016 at 5:11 PM, Steve Ebersole wrote:
> TLDR: Should we adjust to
+1
On Fri, Sep 30, 2016 at 7:02 PM, Steve Ebersole wrote:
> The JPA spec specifically says:
>
>
> Either positional or named parameters may be used. Positional and named
> parameters must not be mixed in a single query.
>
>
> I was thinking about how it does not make sense to mix these in a qu
+1 for always disallowing
On Fri, Sep 30, 2016 at 5:06 PM, andrea boriero wrote:
> +1 for always disallowing
>
> On 30 September 2016 at 17:02, Steve Ebersole wrote:
>
>> The JPA spec specifically says:
>>
>>
>> Either positional or named parameters may be used. Positional and named
>> paramete
+1 for always disallowing
On 30 September 2016 at 17:02, Steve Ebersole wrote:
> The JPA spec specifically says:
>
>
> Either positional or named parameters may be used. Positional and named
> parameters must not be mixed in a single query.
>
>
> I was thinking about how it does not make sense
The JPA spec specifically says:
Either positional or named parameters may be used. Positional and named
parameters must not be mixed in a single query.
I was thinking about how it does not make sense to mix these in a query
(its confusing) and went looking to see what, if anything, the spec had
reading the jira comments I think yes we should.
On 30 September 2016 at 15:11, Steve Ebersole wrote:
> TLDR: Should we adjust to allow Dialect to know the "context" of where the
> remapping is requested?
>
> Ah Oracle...
>
> So this comes from the fact that Oracle does not support a BOOLEAN
> d
TLDR: Should we adjust to allow Dialect to know the "context" of where the
remapping is requested?
Ah Oracle...
So this comes from the fact that Oracle does not support a BOOLEAN
datatype. Well kind of. It does not support a BOOLEAN datatype in its
"SQL engine". However, in PL/SQL it does in f
Due to troubles with my Nexus account the release is not yet completed
anyway It's now possible to push to master.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Please do not push anything to master branch.
Thanks,
Andrea
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
12 matches
Mail list logo
