-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql: JDBC not happy about results for DROP and CREATE #4538
Comments
After investigating the network traces, two observations:
|
One more investigation. I changed the test to use CREATE instead of DROP, so as to avoid red herrings around pg's "Notice" message. Here is a compared network trace (left: pg; right: cdb). The difference starts here:
As can be seen here, the transaction is aborted when CREATE completes. Note how cockroach's CREATE returns rows, whereas pg's doesn't. |
This sounds to me like a beta bug (but then again many things sounds like beta bugs to me:)) particularly if this is triggered by some framework? |
Looks like BEGIN also seems to return some rows in cockroach. Don't know On Sat, Feb 20, 2016 at 12:18 PM, kena notifications@github.com wrote:
|
I meant the client aborts the transaction (with a rollback) because it's not happy with the results of create. See the exception message in the initial issue description.Sent from my Android device with K-9 Mail. Please excuse my brevity. |
To reproduce:
This should output:
|
From there if you are using the local instance you can run |
While looking at #4036 |
After applyting #4537, I run into the next error:
This issue is occuring when JDBC sends "DROP TABLE IF NOT EXISTS TEST" to the db.
The network trace for the CockroachDB connection ( test.cdb.txt ) and a reference using PostgreSQL ( test.pg.txt ) are attached.
The text was updated successfully, but these errors were encountered: