| Lists: | pgsql-jdbc |
|---|
| From: | Xavier Poinsard <xpoinsard(at)openpricer(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Tests for prepared insert statements |
| Date: | 2004-11-17 15:28:37 |
| Message-ID: | cnfqn2$99h$2@sea.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
Hi,
Since I was suspecting the driver, I wrote a two tests regarding
prepared insert statements. May be they could be included.
Xavier.
| Attachment | Content-Type | Size |
|---|---|---|
| PreparedInsertTest.diff | text/plain | 5.3 KB |
| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Xavier Poinsard <xpoinsard(at)openpricer(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Tests for prepared insert statements |
| Date: | 2004-11-17 19:16:47 |
| Message-ID: | Pine.BSO.4.56.0411171410400.4002@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
On Wed, 17 Nov 2004, Xavier Poinsard wrote:
> Hi,
> Since I was suspecting the driver, I wrote a two tests regarding
> prepared insert statements. May be they could be included.
>
Could you describe what additional code paths this is testing? Comparing
it to BatchExecuteTest you seem to be doing an INSERT vs an UPDATE and you
test a few additional datatypes. It doesn't seem to be worth a whole new
TestCase for this. Am I missing something? If not perhaps just modifying
the existing BatchExecuteTest to use more datatypes would be the way to
go.
Kris Jurka