[jira] Commented: (DERBY-3936) Add CharacterStreamDescriptor

[ https://issues.apache.org/jira/browse/DERBY-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645763#action_12645763 ] Knut Anders Hatlen commented on DERBY-3936: --- I agree that the builder pattern is

[jira] Created: (DERBY-3940) Dropping a column does not drop triggers which mention that column

Dropping a column does not drop triggers which mention that column -- Key: DERBY-3940 URL: https://issues.apache.org/jira/browse/DERBY-3940 Project: Derby Issue Type: Bug

[jira] Updated: (DERBY-3940) Dropping a column does not drop triggers which mention that column

[ https://issues.apache.org/jira/browse/DERBY-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3940: - Attachment: dropColumnWithTrigger.sql Triggers.java Attaching a test case: 1)

[jira] Resolved: (DERBY-3770) Create a utility class for skipping data in an InputStream

[ https://issues.apache.org/jira/browse/DERBY-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-3770. --- Resolution: Fixed Fix Version/s: 10.5.0.0 The rest of the methods are working

[jira] Commented: (DERBY-581) Modify SQL to skip N rows of the result and return the next M rows

[ https://issues.apache.org/jira/browse/DERBY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645773#action_12645773 ] Knut Anders Hatlen commented on DERBY-581: -- Is there actually a way to order and

[jira] Commented: (DERBY-3634) Cannot use row_number() in ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645775#action_12645775 ] Knut Anders Hatlen commented on DERBY-3634: --- There's a similar problem when you

[jira] Commented: (DERBY-3936) Add CharacterStreamDescriptor

[ https://issues.apache.org/jira/browse/DERBY-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645780#action_12645780 ] Kristian Waagan commented on DERBY-3936: The reason I added a constructor to the

[jira] Commented: (DERBY-3935) Introduce interface for a position aware stream

[ https://issues.apache.org/jira/browse/DERBY-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645782#action_12645782 ] Knut Anders Hatlen commented on DERBY-3935: --- The patch looks fine to me. +1 to

[jira] Commented: (DERBY-3935) Introduce interface for a position aware stream

[ https://issues.apache.org/jira/browse/DERBY-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645785#action_12645785 ] Knut Anders Hatlen commented on DERBY-3935: --- By the way, would it make sense at

[jira] Commented: (DERBY-3940) Dropping a column does not drop triggers which mention that column

[ https://issues.apache.org/jira/browse/DERBY-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645788#action_12645788 ] Rick Hillegas commented on DERBY-3940: -- Here's my quick analysis of the problem.

[jira] Commented: (DERBY-3936) Add CharacterStreamDescriptor

[ https://issues.apache.org/jira/browse/DERBY-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645792#action_12645792 ] Knut Anders Hatlen commented on DERBY-3936: --- Having default values of false and

[jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual

[ https://issues.apache.org/jira/browse/DERBY-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645793#action_12645793 ] Dag H. Wanvik commented on DERBY-2389: -- Thanks for this improvement, Kim! I notice

[jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual

[ https://issues.apache.org/jira/browse/DERBY-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645795#action_12645795 ] Dag H. Wanvik commented on DERBY-2389: -- I see it is still in Tuning, I guess what I am

Re: Share read-only rows across multiple databases

Matt Kendall [EMAIL PROTECTED] writes: I need functionality in Derby that I don't think it currently provides, so I'm looking to extend Derby to provide it. As part of the product that I'm working on, I'll be automatically installing Derby databases in a standalone server mode. Each database

[jira] Commented: (DERBY-3035) Cannot restore backups without BACKUP.HISTORY file

[ https://issues.apache.org/jira/browse/DERBY-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645801#action_12645801 ] Kathey Marsden commented on DERBY-3035: --- If there are no comments. I'll check this in

[jira] Commented: (DERBY-3940) Dropping a column does not drop triggers which mention that column

[ https://issues.apache.org/jira/browse/DERBY-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645803#action_12645803 ] Dag H. Wanvik commented on DERBY-3940: -- It seems to me the code in

[jira] Commented: (DERBY-1107) For existing databases JDBC metadata queries do not get updated properly between maintenance versions.

[ https://issues.apache.org/jira/browse/DERBY-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645807#action_12645807 ] Knut Anders Hatlen commented on DERBY-1107: --- It sounds safe to me too, as long as

Re: Share read-only rows across multiple databases

Hi Matt, Knut has just suggested a candidate solution involving table functions. At first blush it seems to me that your problem has two pieces to it: the SELECT piece and the INSERT/UPDATE/DELETE piece. For the SELECT piece, it seems to me that your current solution will work on Derby as

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (6 issues) Subscriber: derby-dev Key Summary DERBY-2389 DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual https://issues.apache.org/jira/browse/DERBY-2389 DERBY-1107 For

[jira] Commented: (DERBY-3939) IllegalMonitorStateException in PreparedStatement.executeUpdate()

[ https://issues.apache.org/jira/browse/DERBY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645756#action_12645756 ] Knut Anders Hatlen commented on DERBY-3939: --- Caused by:

[jira] Commented: (DERBY-1107) For existing databases JDBC metadata queries do not get updated properly between maintenance versions.

[ https://issues.apache.org/jira/browse/DERBY-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645814#action_12645814 ] Kathey Marsden commented on DERBY-1107: --- It will get changed on any version change.

[jira] Commented: (DERBY-581) Modify SQL to skip N rows of the result and return the next M rows

[ https://issues.apache.org/jira/browse/DERBY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645816#action_12645816 ] A B commented on DERBY-581: --- Is there actually a way to order and limit at the same time? There

[jira] Commented: (DERBY-3937) Select count(*) scans all the rows (and is therefore slow with big tables), is the amount of rows not available/known for example in index ?

[ https://issues.apache.org/jira/browse/DERBY-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645753#action_12645753 ] Knut Anders Hatlen commented on DERBY-3937: --- So back to my original question -

Regression Test Report - Daily 711922 - Sun DBTG

[Auto-generated mail] *Daily* 711922/2008-11-06 18:01:56 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA suitesAll NA NA NANA jdbcapiAutoLoad NA

[jira] Commented: (DERBY-2389) DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual

[ https://issues.apache.org/jira/browse/DERBY-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645808#action_12645808 ] Kim Haase commented on DERBY-2389: -- I'm glad you noticed this, Dag, because I was

Re: Share read-only rows across multiple databases

I don't understand the complexity of the INSERT/UPDATE/DELETE piece. Why does the application need to issue INSERT/UPDATE/DELETE against the view rather than directly against the user-specific table? Because nothing's ever easy :). Long story short, we're currently developing an automatic

[jira] Created: (DERBY-3941) Unsafe use of DataInput.skipBytes() in StoredPage and StoredFieldHeader

Unsafe use of DataInput.skipBytes() in StoredPage and StoredFieldHeader --- Key: DERBY-3941 URL: https://issues.apache.org/jira/browse/DERBY-3941 Project: Derby Issue Type:

[jira] Updated: (DERBY-481) implement SQL generated columns

[ https://issues.apache.org/jira/browse/DERBY-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-481: Attachment: derby-481-14-ab-dropColumn.diff Attaching derby-481-14-ab-dropColumn.diff. Running

[jira] Commented: (DERBY-1107) For existing databases JDBC metadata queries do not get updated properly between maintenance versions.

[ https://issues.apache.org/jira/browse/DERBY-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645869#action_12645869 ] Knut Anders Hatlen commented on DERBY-1107: --- Thanks for verifying. And +1 to

[jira] Commented: (DERBY-481) implement SQL generated columns

[ https://issues.apache.org/jira/browse/DERBY-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12645891#action_12645891 ] Rick Hillegas commented on DERBY-481: - Tests ran cleanly for me on

fixture ReplicationRun_Local_3_p2.....StopMaster_DISABLED()

The contents of the fixture testReplication_Local_3_p2_StateTests_smallInsert_immediateStopMaster_DISABLED() in test ReplicationRun_Local_3_p2 are commented out, which results in an attempt to call teardown, i.e. org.apache.derby.drda.NetworkServerControl shutdown while there is no server started,