| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | Darin Ohashi <DOhashi(at)maplesoft(dot)com> |
| Cc: | 'Oliver Jowett' <oliver(at)opencloud(dot)com>, Fernando Nasser <fnasser(at)redhat(dot)com>, Kim Ho <kho(at)redhat(dot)com>, Barry Lind <blind(at)xythos(dot)com>, pgsql-jdbc-list <pgsql-jdbc(at)postgresql(dot)org>, Dave Cramer <Dave(at)micro-automation(dot)net> |
| Subject: | Re: IN clauses via setObject(Collection) [Was: Re: Prepare |
| Date: | 2003-07-21 20:31:33 |
| Message-ID: | 3F1C4DA5.4040402@openratings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>
>
>So, yes you should be able to create a set datatype and pass that into the
>PreparedStatment (JDBC allows for this using the SQLData interface, I don't know
>if postgresql supports it),
>
I know, that it doesn't
> but the data that is representing a set datatype
>would not be able to be inserted where SQL set Syntax is expected.
>
Why the hell not???
> The set
>datatype and the SQL set Syntax are completely distinct objects.
>
>
An int datatype and an int syntax are two distinct objects too :-)
That's precisely the job of the JDBC driver to convert datatypes I pass
in into their representation with the correct syntax that backend would
understand.
I would have no use of the driver doing anything else - what's the point
in passign data in if the syntax it gets converted into isn't understood
by the server?
Dima
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2003-07-21 20:33:48 | Re: jdbc batch performance problem |
| Previous Message | Darin Ohashi | 2003-07-21 20:20:45 | Re: IN clauses via setObject(Collection) [Was: Re: Prepare |