Re: [VOTE] 10.14.2.0 release

+1 On Sun, Apr 8, 2018 at 2:44 PM, Bryan Pendleton wrote: > Please test-drive the 10.14.2.0 candidate, then vote on whether to > accept it as a Derby release. The candidate lives at: > > http://people.apache.org/~bpendleton/derby/rc-10.14.2.0/ > > Since I have some

Re: Need some help in trying to figure out a corrupt database

for the review of the party to whom it is addressed. If you have received this transmission in error, please notify the sender immediately and discard the original message and any attachment(s). . -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

Re: collation/territory info -- where is it stored?

like the "collation_ids" array in impl.store.access.btree.Btree. Can anyone point me in the right direction? thanks, bryan -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

Re: are there any historical test run results available any more for derby?

to the Jenkins runs that Myrna noted at builds.apache.org. I'll try to find time to do that soon. bryan . thanks bryan, i was just going to check if the large data runs were there. i think ibm used to run them. /mikem -- email:Mike Matrigali - mikema...@gmail.com linkedin: https

are there any historical test run results available any more for derby?

ults/ <http://people.apache.org/%7Emyrnavl/derby_test_results/> -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

Re: Is there any debug logging available when a database is being recovered

r the review of the party to whom it is addressed. If you have received this transmission in error, please notify the sender immediately and discard the original message and any attachment(s). -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

[jira] [Commented] (DERBY-6884) SYSCS_IMPORT_TABLE_LOBS_FROM_EXTFILE can't import more than Integer.MAX_VALUE bytes of blob data

[ https://issues.apache.org/jira/browse/DERBY-6884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264183#comment-15264183 ] Mike Matrigali commented on DERBY-6884: --- there use to be a test suite for tests like

[jira] [Commented] (DERBY-6858) Apache Derby simple update statement performance becomes 1500% worse when adding one byte to a column

[ https://issues.apache.org/jira/browse/DERBY-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156177#comment-15156177 ] Mike Matrigali commented on DERBY-6858: --- note that the decision between these two plans is even more

[jira] [Commented] (DERBY-6858) Apache Derby simple update statement performance becomes 1500% worse when adding one byte to a column

[ https://issues.apache.org/jira/browse/DERBY-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156174#comment-15156174 ] Mike Matrigali commented on DERBY-6858: --- The row count estimates the optimizer is using are likely

[jira] [Created] (DERBY-6874) add table size information to optimizer plan information printed

Mike Matrigali created DERBY-6874: - Summary: add table size information to optimizer plan information printed Key: DERBY-6874 URL: https://issues.apache.org/jira/browse/DERBY-6874 Project: Derby

[jira] [Commented] (DERBY-6873) handle btree rebalance case when it can't get table level lock.

[ https://issues.apache.org/jira/browse/DERBY-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156165#comment-15156165 ] Mike Matrigali commented on DERBY-6873: --- simple solution would be to give the rebalance operation

[jira] [Commented] (DERBY-6873) handle btree rebalance case when it can't get table level lock.

[ https://issues.apache.org/jira/browse/DERBY-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156161#comment-15156161 ] Mike Matrigali commented on DERBY-6873: --- elegant solution would be to do the operation without

[jira] [Updated] (DERBY-6873) handle btree rebalance case when it can't get table level lock.

[ https://issues.apache.org/jira/browse/DERBY-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6873: -- Summary: handle btree rebalance case when it can't get table level lock. (was: hand btree

[jira] [Created] (DERBY-6873) hand btree rebalance case when it can't get table level lock.

Mike Matrigali created DERBY-6873: - Summary: hand btree rebalance case when it can't get table level lock. Key: DERBY-6873 URL: https://issues.apache.org/jira/browse/DERBY-6873 Project: Derby

[jira] [Assigned] (DERBY-1068) change of store contract: online compress operations should not share any locks with user transactions

[ https://issues.apache.org/jira/browse/DERBY-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali reassigned DERBY-1068: - Assignee: (was: Mike Matrigali) unlikely to look at this in near future, unassigning

[jira] [Assigned] (DERBY-6775) add to testBlobLinkedListReclamationOnRollback() test to check that free space is used on subsequent inserts

[ https://issues.apache.org/jira/browse/DERBY-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali reassigned DERBY-6775: - Assignee: (was: Mike Matrigali) unlikely to look at this in near future, unassigning

[jira] [Assigned] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali reassigned DERBY-6784: - Assignee: (was: Mike Matrigali) unlikely to look at this in near future, unassigning

[jira] [Assigned] (DERBY-2338) improve page allocation when there are many threaded inserts to same table .

[ https://issues.apache.org/jira/browse/DERBY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali reassigned DERBY-2338: - Assignee: (was: Mike Matrigali) unlikely to look at this in near future, unassigning

[jira] [Commented] (DERBY-6858) Apache Derby simple update statement performance becomes 1500% worse when adding one byte to a column

[ https://issues.apache.org/jira/browse/DERBY-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15156137#comment-15156137 ] Mike Matrigali commented on DERBY-6858: --- note that deferred update is a different concept than

[jira] [Created] (DERBY-6872) change optmizer plan output to include information about if cardinality stats have been gathered.

Mike Matrigali created DERBY-6872: - Summary: change optmizer plan output to include information about if cardinality stats have been gathered. Key: DERBY-6872 URL: https://issues.apache.org/jira/browse/DERBY-6872

[jira] [Commented] (DERBY-6858) Apache Derby simple update statement performance becomes 1500% worse when adding one byte to a column

[ https://issues.apache.org/jira/browse/DERBY-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155843#comment-15155843 ] Mike Matrigali commented on DERBY-6858: --- I also want to add that unfortunately one can no longer

[jira] [Commented] (DERBY-6858) Apache Derby simple update statement performance becomes 1500% worse when adding one byte to a column

[ https://issues.apache.org/jira/browse/DERBY-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15155838#comment-15155838 ] Mike Matrigali commented on DERBY-6858: --- I am coming late to this discussion. mostly what i looked

Re: Exception running RunOptimizerTest

) at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:334) at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1814) ... 18 more BUILD SUCCESSFUL (total time: 2 seconds) -- email:Mike Matrigali - mikema...@gmail.com linkedin: https

are there any daily public test results being published for derby any more?

. This is not surprising given that both ibm and oracle have reduced or eliminated their derby support. Just checking if there is another place to find this info. I know derby it tied into the per change build system. maybe there are tests run also or could be? -- email:Mike Matrigali - mikema

Re: testing 10.12.1.1

list. Also, it would be good to see some more platform test results at http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting. Thanks! -Rick -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

[jira] [Commented] (DERBY-6837) ERROR 40XL1 due to incorrect lock

[ https://issues.apache.org/jira/browse/DERBY-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909802#comment-14909802 ] Mike Matrigali commented on DERBY-6837: --- each connection to derby runs in it's own transaction

[jira] [Commented] (DERBY-6837) ERROR 40XL1 due to incorrect lock

[ https://issues.apache.org/jira/browse/DERBY-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905784#comment-14905784 ] Mike Matrigali commented on DERBY-6837: --- if you can not reproduce, please add to your problem

[jira] [Commented] (DERBY-6837) ERROR 40XL1 due to incorrect lock

[ https://issues.apache.org/jira/browse/DERBY-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14905788#comment-14905788 ] Mike Matrigali commented on DERBY-6837: --- derby was just not designed with concurrent ddl in mind

[jira] [Commented] (DERBY-6833) NPE in IndexRowGenerator.getExecutionFactory()

[ https://issues.apache.org/jira/browse/DERBY-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741870#comment-14741870 ] Mike Matrigali commented on DERBY-6833: --- is it likely or not that your system may have been

[jira] [Commented] (DERBY-6833) NPE in IndexRowGenerator.getExecutionFactory()

[ https://issues.apache.org/jira/browse/DERBY-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741869#comment-14741869 ] Mike Matrigali commented on DERBY-6833: --- can you post a complete derby.log? >

Re: [VOTE] Sunsetting support for Java 7

that this policy will require any changes to user code. . -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

Re: Derby received an error "ERROR XSDG0: Page Page(1325564,Container(0, 30832)) could not be read from disk."

implement a real partitioning scheme that would be more efficient especially on the queries and add this capability back into derby, so if anyone has any ideas on this, I am all ears. Brett -Original Message- From: mike matrigali [mailto:mikema...@gmail.com] Sent: Friday, September 04

Re: Derby received an error "ERROR XSDG0: Page Page(1325564,Container(0, 30832)) could not be read from disk."

uggestions about how to diagnose the conglomerate in question in more detail, and also some observations about possible causes and possible courses of action you can take subsequently. thanks, bryan -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

Re: 10.12.1 release

of the 10.12.1 release notes at http://svn.apache.org/viewvc/db/derby/code/trunk/RELEASE-NOTES.html?view=co Is there anything which the community wants to wrap up before I build the first release candidate next Monday (2015-08-07)? Thanks, -Rick -- email:Mike Matrigali - mikema...@gmail.com

[jira] [Commented] (DERBY-6826) SOA PROD - The state of datasource DifJavaDbDataSource, application domain-level is Suspended.

[ https://issues.apache.org/jira/browse/DERBY-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631586#comment-14631586 ] Mike Matrigali commented on DERBY-6826: --- given the current information no progress

Re: XmlVTI.next() invocation of printStackTrace()

the test results rather ugly... What would be the downside if I removed that printStackTrace() call? thanks, bryan -- email:Mike Matrigali - mikema...@gmail.com linkedin: https://www.linkedin.com/in/MikeMatrigali

[jira] [Commented] (DERBY-6818) java.lang.OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-6818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582260#comment-14582260 ] Mike Matrigali commented on DERBY-6818: --- a couple of ddl based workarounds that may

should we announce jdk17 sunset also with the 10.12 release?

as they are completely dependent on volunteers adding enhancements and doing the releases. I would be in favor of sunsetting jdk17 in 10.13 also, and announcing that in the 10.12 release. Following a vote by the community, but first wanted to see if there is informal feedback to the contrary. -- email:Mike

[jira] [Commented] (DERBY-6809) Java 1.8 feature use

[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566034#comment-14566034 ] Mike Matrigali commented on DERBY-6809: --- I see no reason to work off any version

[jira] [Commented] (DERBY-6809) Java 1.8 feature use

[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566050#comment-14566050 ] Mike Matrigali commented on DERBY-6809: --- Some generic comments on possible

[jira] [Commented] (DERBY-6809) Java 1.8 feature use

[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566052#comment-14566052 ] Mike Matrigali commented on DERBY-6809: --- See derby.storage.sortBufferMax property

[jira] [Commented] (DERBY-6809) Java 1.8 feature use

[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552425#comment-14552425 ] Mike Matrigali commented on DERBY-6809: --- i would add that you should make sure

[jira] [Commented] (DERBY-6809) Java 1.8 feature use

[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546997#comment-14546997 ] Mike Matrigali commented on DERBY-6809: --- Not sure what exactly is being proposed

[jira] [Commented] (DERBY-6809) Java 1.8 feature use

[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546998#comment-14546998 ] Mike Matrigali commented on DERBY-6809: --- There was a VOTE on sunsetting jdk6 support

[jira] [Commented] (DERBY-6797) If a (machine/jvm) crash happens during hard upgrade, derby does not roll back the upgrade.

[ https://issues.apache.org/jira/browse/DERBY-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347375#comment-14347375 ] Mike Matrigali commented on DERBY-6797: --- To debug I would suggest setting properties

Open letter to the Derby community

, subsidized feature development and intensive bug-fixing have tapered off. Some committers would be happy to form a company which sells Derby support. Naturally, this depends on whether there is sufficient interest on the part of Derby users. If you are interested, then please contact Mike Matrigali

[jira] [Commented] (DERBY-6796) Impossible to define new sub-subprotocols

[ https://issues.apache.org/jira/browse/DERBY-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341155#comment-14341155 ] Mike Matrigali commented on DERBY-6796: --- are you able/inclined to provide a junit

[jira] [Commented] (DERBY-6791) Google Summer of Code 2015: Derby bug fixing

[ https://issues.apache.org/jira/browse/DERBY-6791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14328099#comment-14328099 ] Mike Matrigali commented on DERBY-6791: --- you need to login. then there is an assign

[jira] [Commented] (DERBY-6794) SYSCS_UTIL.SYSCS_GET_RUNTIMESTATISTICS(1) returns a long varchar (32,700)

[ https://issues.apache.org/jira/browse/DERBY-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14316915#comment-14316915 ] Mike Matrigali commented on DERBY-6794: --- It might be safest to propose a new get

[jira] [Commented] (DERBY-6792) Could not execute JDBC batch update

[ https://issues.apache.org/jira/browse/DERBY-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315493#comment-14315493 ] Mike Matrigali commented on DERBY-6792: --- Another question is does your product fork

[jira] [Commented] (DERBY-6792) Could not execute JDBC batch update

[ https://issues.apache.org/jira/browse/DERBY-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315491#comment-14315491 ] Mike Matrigali commented on DERBY-6792: --- In order to fix this we will need more

[jira] [Commented] (DERBY-6793) Stream or LOG value cannot be retrieved more than once

[ https://issues.apache.org/jira/browse/DERBY-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14312741#comment-14312741 ] Mike Matrigali commented on DERBY-6793: --- user reports issue resulted from changes

[jira] [Updated] (DERBY-5936) AllocPage.ReadContainerInfo throws ArrayIndexOutOfBoundsException at arraycopy

[ https://issues.apache.org/jira/browse/DERBY-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5936: -- Labels: derby_triage10_12 (was: ) 10.12 triage effort. Issue is serious, but without repro

[jira] [Updated] (DERBY-5980) Extremely slow roll forward when booting database that wasn't properly closed

[ https://issues.apache.org/jira/browse/DERBY-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5980: -- Labels: derby_triage10_12 (was: ) 10.12 bug triage effort. No more detail information

[jira] [Resolved] (DERBY-6271) Backup error when in-memory with jar

[ https://issues.apache.org/jira/browse/DERBY-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali resolved DERBY-6271. --- Resolution: Cannot Reproduce no more info was provided to a query over a year ago. closing

[jira] [Updated] (DERBY-5980) Extremely slow roll forward when booting database that wasn't properly closed

[ https://issues.apache.org/jira/browse/DERBY-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5980: -- Urgency: Normal Extremely slow roll forward when booting database that wasn't properly closed

[jira] [Updated] (DERBY-5738) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE only returns to the OS pages in the last extent

[ https://issues.apache.org/jira/browse/DERBY-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5738: -- Urgency: Urgent SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE only returns to the OS pages

[jira] [Updated] (DERBY-6153) Derby5234Test..test_03_triggeringEdge: sanity AssertFailure during LogToFile call to markCorrupted after IOException

[ https://issues.apache.org/jira/browse/DERBY-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6153: -- Labels: derby_triage10_12 (was: ) 10.12 bug triage effort. Derby5234Test

[jira] [Updated] (DERBY-6425) DB got corrupted during the heavy operations.

[ https://issues.apache.org/jira/browse/DERBY-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6425: -- Labels: derby_triage10_12 (was: ) 10.12 triage effort. Do you plan on adding any more

[jira] [Updated] (DERBY-5738) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE only returns to the OS pages in the last extent

[ https://issues.apache.org/jira/browse/DERBY-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5738: -- Issue fix info: High Value Fix Bug behavior facts: Seen in production

[jira] [Updated] (DERBY-6271) Backup error when in-memory with jar

[ https://issues.apache.org/jira/browse/DERBY-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6271: -- Labels: derby_triage10_12 (was: ) 10.12 bug triage effort. Backup error when in-memory

[jira] [Updated] (DERBY-6153) Derby5234Test..test_03_triggeringEdge: sanity AssertFailure during LogToFile call to markCorrupted after IOException

[ https://issues.apache.org/jira/browse/DERBY-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6153: -- Urgency: Low Derby5234Test..test_03_triggeringEdge: sanity AssertFailure during LogToFile

[jira] [Resolved] (DERBY-6425) DB got corrupted during the heavy operations.

[ https://issues.apache.org/jira/browse/DERBY-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali resolved DERBY-6425. --- Resolution: Cannot Reproduce no more work likely at the moment. workaround seems to work

[jira] [Updated] (DERBY-5963) Memory leak when shutting down Derby system

[ https://issues.apache.org/jira/browse/DERBY-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5963: -- Issue fix info: Repro attached Labels: derby_triage10_12 (was: ) 10.12 triage

[jira] [Commented] (DERBY-6774) background post commit threads cause ASSERTS/errors on interaction with alter table add column

[ https://issues.apache.org/jira/browse/DERBY-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14277583#comment-14277583 ] Mike Matrigali commented on DERBY-6774: --- at least this particular repro seems caused

[jira] [Resolved] (DERBY-6774) background post commit threads cause ASSERTS/errors on interaction with alter table add column

[ https://issues.apache.org/jira/browse/DERBY-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali resolved DERBY-6774. --- Resolution: Fixed Fix Version/s: 10.12.0.0 background post commit threads cause

[jira] [Commented] (DERBY-6725) Add a system function which returns the name of the database.

[ https://issues.apache.org/jira/browse/DERBY-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14274186#comment-14274186 ] Mike Matrigali commented on DERBY-6725: --- I too ran into problems when I first

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14253662#comment-14253662 ] Mike Matrigali commented on DERBY-6785: --- ij uses the same communication interfaces

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14253686#comment-14253686 ] Mike Matrigali commented on DERBY-6785: --- Is it too late to consider adding

[jira] [Updated] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6784: -- Attachment: DERBY_6784_diff_1.txt preliminary patch, not ready for commit. This change models

[jira] [Updated] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6784: -- Attachment: current_perf.txt Running attached benchmark program against trunk, insane jars

[jira] [Updated] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6784: -- Attachment: Derby47PerformanceTest.java benchmark from DERBY-47, minor changes to get it to try

[jira] [Updated] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6784: -- Attachment: patch_1_perf.txt Running attached benchmark program against DERBY_6784_diff_1.txt

[jira] [Commented] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254368#comment-14254368 ] Mike Matrigali commented on DERBY-6784: --- some thoughts so far: 1) costing

[jira] [Commented] (DERBY-6124) Marshalling error in JDBCDriverTest as part of CompatibilityTest

[ https://issues.apache.org/jira/browse/DERBY-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251926#comment-14251926 ] Mike Matrigali commented on DERBY-6124: --- The latest derby releases can be found

[jira] [Commented] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251938#comment-14251938 ] Mike Matrigali commented on DERBY-6784: --- Good questions. I am somewhat out of my

[jira] [Comment Edited] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251938#comment-14251938 ] Mike Matrigali edited comment on DERBY-6784 at 12/18/14 6:00 PM

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252376#comment-14252376 ] Mike Matrigali commented on DERBY-6785: --- I am still struggling to understand if you

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252381#comment-14252381 ] Mike Matrigali commented on DERBY-6785: --- what machine is the derby.log that you

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252387#comment-14252387 ] Mike Matrigali commented on DERBY-6785: --- can you provide exact alter table statement

what client/server compatibility is Derby supposed to support?

What level of client/server compatibility is Derby meant to support. This is just about the derby version of the software on the client machine and the version of the software on the server machine. Not asking anything about the version used to create the database being accessed. Is any

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252624#comment-14252624 ] Mike Matrigali commented on DERBY-6785: --- thanks that is much clearer. Can you give

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252630#comment-14252630 ] Mike Matrigali commented on DERBY-6785: --- I don't have much experience with client

[jira] [Comment Edited] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252624#comment-14252624 ] Mike Matrigali edited comment on DERBY-6785 at 12/19/14 12:28 AM

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252649#comment-14252649 ] Mike Matrigali commented on DERBY-6785: --- could you try the following. Create a new

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252935#comment-14252935 ] Mike Matrigali commented on DERBY-6785: --- Rick, my reading of the derby.log

[jira] [Commented] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252951#comment-14252951 ] Mike Matrigali commented on DERBY-6785: --- I agree with rick, derby explicitly does

[jira] [Comment Edited] (DERBY-6785) Latest JDBC driver from 10.11.1.1 gives exception when trying to connect to 10.10.2.0

[ https://issues.apache.org/jira/browse/DERBY-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252951#comment-14252951 ] Mike Matrigali edited comment on DERBY-6785 at 12/19/14 5:14 AM

[jira] [Created] (DERBY-6784) change optimizer to choose in list multiprobe more often

Mike Matrigali created DERBY-6784: - Summary: change optimizer to choose in list multiprobe more often Key: DERBY-6784 URL: https://issues.apache.org/jira/browse/DERBY-6784 Project: Derby

[jira] [Commented] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250849#comment-14250849 ] Mike Matrigali commented on DERBY-6784: --- The issue described in DERBY-6300

[jira] [Resolved] (DERBY-6300) row locks incorrectly taken for rows that do not match SELECT predicate

[ https://issues.apache.org/jira/browse/DERBY-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali resolved DERBY-6300. --- Resolution: Unresolved While not optimal the behavior described in DERBY-6300 is expected

[jira] [Commented] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250857#comment-14250857 ] Mike Matrigali commented on DERBY-6784: --- original work for multi-probe IN LIST

[jira] [Commented] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250860#comment-14250860 ] Mike Matrigali commented on DERBY-6784: --- In Army's original work

[jira] [Commented] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250874#comment-14250874 ] Mike Matrigali commented on DERBY-6784: --- My plan is to address this issue

[jira] [Assigned] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali reassigned DERBY-6784: - Assignee: Mike Matrigali change optimizer to choose in list multiprobe more often

[jira] [Comment Edited] (DERBY-6784) change optimizer to choose in list multiprobe more often

[ https://issues.apache.org/jira/browse/DERBY-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250874#comment-14250874 ] Mike Matrigali edited comment on DERBY-6784 at 12/18/14 12:29 AM

[jira] [Updated] (DERBY-6782) Unknown page format at page Page(51,Container(0, 1136))

[ https://issues.apache.org/jira/browse/DERBY-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6782: -- Summary: Unknown page format at page Page(51,Container(0, 1136)) (was: Unknow page format

[jira] [Commented] (DERBY-6782) Unknown page format at page Page(51,Container(0, 1136))

[ https://issues.apache.org/jira/browse/DERBY-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244699#comment-14244699 ] Mike Matrigali commented on DERBY-6782: --- from the posted information it does look

[jira] [Commented] (DERBY-6782) Unknown page format at page Page(51,Container(0, 1136))

[ https://issues.apache.org/jira/browse/DERBY-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244702#comment-14244702 ] Mike Matrigali commented on DERBY-6782: --- I should also add that it is clear from

[jira] [Updated] (DERBY-6774) background post commit threads cause ASSERTS/errors on interaction with alter table add column

[ https://issues.apache.org/jira/browse/DERBY-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-6774: -- Summary: background post commit threads cause ASSERTS/errors on interaction with alter table

  1   2   3   4   5   6   7   8   9   10   >