[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional

[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441312 ] Suresh Thalamati commented on DERBY-1953: - I reviewed the latest patch , it looks good. I will commit it, after running the tests. Make FOR EACH

[jira] Commented: (DERBY-1819) couple of small errors in the admin guide documentation of NetworkServerControl() API (shutdown and sysinfo ...)

[ http://issues.apache.org/jira/browse/DERBY-1819?page=comments#action_12440575 ] Suresh Thalamati commented on DERBY-1819: - Thanks for working on this issue , Laura. Changes looks good to me, patch can be committted. +1. /suresh

[jira] Assigned: (DERBY-1240) creating /restoring a db from backup using createFrom with log at different location copies the log from backup to the db dir also.

[ http://issues.apache.org/jira/browse/DERBY-1240?page=all ] Suresh Thalamati reassigned DERBY-1240: --- Assignee: Suresh Thalamati creating /restoring a db from backup using createFrom with log at different location copies the log from backup

Re: [VOTE] 10.2.1.6 release

Rick Hillegas wrote: I have posted a new release candidate, 10.2.1.6, which addresses the structural problems with the previous candidate. Special thanks to Andrew for helping sand this one down. You may find 10.2.1.6 at: http://people.apache.org/~rhillegas/10.2.1.6/ +1 I crashed derby

[jira] Created: (DERBY-1925) Add re-encrytion of database test cases to the upgrade test..

Affects Versions: 10.2.2.0, 10.3.0.0 Reporter: Suresh Thalamati Assigned To: Suresh Thalamati Add a encryption of an un-encrypted database and re-encryption of encrypted database test case to the upgrade test. Please see DERBY-1156 for details about re-encryption feature

[jira] Resolved: (DERBY-1898) can not boot derby if class path contains 10.1 jars first and then 10.2 jars

[ http://issues.apache.org/jira/browse/DERBY-1898?page=all ] Suresh Thalamati resolved DERBY-1898. - Resolution: Invalid Derby is not expected to work correctly, if two versions of derby jar files are present in the classpath. can not boot

Re: Regression Test Failure! - TinderBox_Derby 450726 - Sun DBTG

Hi Ole, In this regression test run, store/OnlineBackupTest1,java failed with similar error that was seen a while ago; (http://issues.apache.org/jira/browse/DERBY-973)DERBY-973. If the test data is still around , it would be great if you could attach all the data in the test directory

[jira] Commented: (DERBY-1898) can not boot derby if class path contains 10.1 jars first and then 10.2 jars

[ http://issues.apache.org/jira/browse/DERBY-1898?page=comments#action_12438594 ] Suresh Thalamati commented on DERBY-1898: - But fixing the above one won't solve the existing problem with old jars, I think the fix for this issues

Re: [jira] Commented: (DERBY-1898) can not boot derby if class path contains 10.1 jars first and then 10.2 jars

Daniel John Debrunner (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1898?page=comments#action_12438595 ] Daniel John Debrunner commented on DERBY-1898: -- Is this expected to be supported? I guess not, users are

[jira] Resolved: (DERBY-1854) SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[ http://issues.apache.org/jira/browse/DERBY-1854?page=all ] Suresh Thalamati resolved DERBY-1854. - Resolution: Fixed committed to 10.2 as part of meg-merge , revision. 449013. SYSCS_COMPRESS_TABLE corrupts table with a single column which

[jira] Resolved: (DERBY-1641) Conglomerate requested does not exist after syscs_import_table with FK

[ http://issues.apache.org/jira/browse/DERBY-1641?page=all ] Suresh Thalamati resolved DERBY-1641. - Fix Version/s: 10.3.0.0 Resolution: Fixed This is a duplicate of DERBY-1854 . Fixed in 10.2 , revision 449013 and in 10.3. revision

[jira] Updated: (DERBY-1854) SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[ http://issues.apache.org/jira/browse/DERBY-1854?page=all ] Suresh Thalamati updated DERBY-1854: Attachment: derby-1854.diff Problem was all the conglomerate descriptor entries in sys.sysconglomerates were not getting updated with new conglomerate

[jira] Updated: (DERBY-1854) SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[ http://issues.apache.org/jira/browse/DERBY-1854?page=all ] Suresh Thalamati updated DERBY-1854: Attachment: derby-1854_v1.diff This patch has same fix as in deryby-1854.diff , Only thing new in this patch is the updates

[jira] Commented: (DERBY-1854) SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[ http://issues.apache.org/jira/browse/DERBY-1854?page=comments#action_12436704 ] Suresh Thalamati commented on DERBY-1854: - Committed to trunk on revision 448758. Thanks for taking time to review the patch , Andrew, Mamta

[jira] Commented: (DERBY-1718) creating an after insert trigger with trigger action involving xml datatype throws java.io.NottSerializableException

[ http://issues.apache.org/jira/browse/DERBY-1718?page=comments#action_12436121 ] Suresh Thalamati commented on DERBY-1718: - Committed to trunk on revision 448085.. creating an after insert trigger with trigger action involving

[jira] Commented: (DERBY-1854) SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[ http://issues.apache.org/jira/browse/DERBY-1854?page=comments#action_12436361 ] Suresh Thalamati commented on DERBY-1854: - debugged this bug little bit , looks like the problem is one of the conglomerate descriptor entries

[jira] Assigned: (DERBY-1854) SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[ http://issues.apache.org/jira/browse/DERBY-1854?page=all ] Suresh Thalamati reassigned DERBY-1854: --- Assignee: Suresh Thalamati SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key

[jira] Commented: (DERBY-1838) Derby allows dual boot which can cause corruption of databases with JVM's lower than 1.4.2 on non-windows systems

[ http://issues.apache.org/jira/browse/DERBY-1838?page=comments#action_12435968 ] Suresh Thalamati commented on DERBY-1838: - you are right John. Dual boot through multiple JVMs is prevented on Unix from JDK1.4 (1.4.0) using

[jira] Commented: (DERBY-1718) creating an after insert trigger with trigger action involving xml datatype throws java.io.NottSerializableException

[ http://issues.apache.org/jira/browse/DERBY-1718?page=comments#action_12436061 ] Suresh Thalamati commented on DERBY-1718: - I did a quick review of this patch. One change that caught my attention is the new format id added

[jira] Updated: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.

[ http://issues.apache.org/jira/browse/DERBY-1786?page=all ] Suresh Thalamati updated DERBY-1786: Component/s: Store Fix Version/s: 10.2.1.0 10.3.0.0 committed to 10.2 as part of meg-merge done by Rick. on revision 446700

[jira] Resolved: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.

[ http://issues.apache.org/jira/browse/DERBY-1786?page=all ] Suresh Thalamati resolved DERBY-1786. - Resolution: Fixed a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot

Re: [jira] Commented: (DERBY-801) Allow parallel access to data files.

Anders Morken wrote: Suresh Thalamati (JIRA): [ http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12434613 ] snip .. RAFContainerFactory.java Logic in this new class seems to be deciding whether to load RafContainer.java

[jira] Commented: (DERBY-801) Allow parallel access to data files.

[ http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12435610 ] Suresh Thalamati commented on DERBY-801: Hi Knut , Patch is good. It is ok with me , if you would like to commit the current patch and let Anders

[jira] Commented: (DERBY-1718) creating an after insert trigger with trigger action involving xml datatype throws java.io.NottSerializableException

[ http://issues.apache.org/jira/browse/DERBY-1718?page=comments#action_12435616 ] Suresh Thalamati commented on DERBY-1718: - Thanks for working on this issue Yip. I will run derbyall and commit the patch. Thanks a lot for taking

[jira] Commented: (DERBY-1706) NullPointerException occurs when trying to create a table in schema SESSION

[ http://issues.apache.org/jira/browse/DERBY-1706?page=comments#action_12435075 ] Suresh Thalamati commented on DERBY-1706: - Hi Mamta, just a general question: Why is it necessary to allow users to create a non-temporary tables

[jira] Commented: (DERBY-801) Allow parallel access to data files.

[ http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12434613 ] Suresh Thalamati commented on DERBY-801: Thanks for working on this issue, Anders. I really like your solution to solve this issue. Patch is very good, I

[jira] Commented: (DERBY-1618) store/BootAllTest.junit fails on with jdk13 based jvms

[ http://issues.apache.org/jira/browse/DERBY-1618?page=comments#action_12434495 ] Suresh Thalamati commented on DERBY-1618: - Committed DERBY-1618_20060912.diff to trunk on revision 443038. store/BootAllTest.junit fails on with jdk13

[jira] Commented: (DERBY-1838) Derby allows dual boot which can cause corruption of databases with JVM's lower than 1.4.2 on non-windows systems

[ http://issues.apache.org/jira/browse/DERBY-1838?page=comments#action_12434071 ] Suresh Thalamati commented on DERBY-1838: - Kathy, I think this is issue not a bug , this is a known problem documented in the developer guide. http

Re: 10.2 plans (was Re: 10.2 licensing issue)

Andrew McIntyre wrote: Taking this over to derby-dev... On 9/11/06, Kathey Marsden [EMAIL PROTECTED] wrote: Many of these regressions sadly have already made their way into 10.1.3 and therefore are being picked up by users for production. I think we need to notify the user community of the

[jira] Updated: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.

[ http://issues.apache.org/jira/browse/DERBY-1786?page=all ] Suresh Thalamati updated DERBY-1786: Attachment: derby-1786.diff The problem was when transaction log spans more than one log file during (re) encryption of the database

[jira] Commented: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.

[ http://issues.apache.org/jira/browse/DERBY-1786?page=comments#action_12434220 ] Suresh Thalamati commented on DERBY-1786: - Committed derby-1786.diff to trunk; revision 442647. a crash during re-encryption of an existing database

[jira] Commented: (DERBY-1618) store/BootAllTest.junit fails on with jdk13 based jvms

[ http://issues.apache.org/jira/browse/DERBY-1618?page=comments#action_12434273 ] Suresh Thalamati commented on DERBY-1618: - I reviewed the latest patch, it look good. I wanted to check with you couple of small changes in the diff

[jira] Commented: (DERBY-1820) In the reference manual the description of backupDir arugument for all the backup procedures is incorrect.

[ http://issues.apache.org/jira/browse/DERBY-1820?page=comments#action_12434294 ] Suresh Thalamati commented on DERBY-1820: - Thanks for volunteering to fix this issue Laura. your suggestion 1 2 looks good. Regarding the 3'rd

[jira] Commented: (DERBY-1820) In the reference manual the description of backupDir arugument for all the backup procedures is incorrect.

[ http://issues.apache.org/jira/browse/DERBY-1820?page=comments#action_12434321 ] Suresh Thalamati commented on DERBY-1820: - The changes looks good, Thanks Laura. +1 In the reference manual the description of backupDir arugument

[jira] Commented: (DERBY-1618) store/BootAllTest.junit fails on with jdk13 based jvms

[ http://issues.apache.org/jira/browse/DERBY-1618?page=comments#action_12433274 ] Suresh Thalamati commented on DERBY-1618: - Thanks for working on this bug, Mryna. I briefly looked at the patch, this issue seems to be related

[jira] Created: (DERBY-1819) couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo ...)

://issues.apache.org/jira/browse/DERBY-1819 Project: Derby Issue Type: Bug Components: Documentation Reporter: Suresh Thalamati 1) in Shutting down by using the API(http://db.apache.org/derby/docs/dev/adminguide/tadminconfig815357.html) I think

[jira] Updated: (DERBY-1819) couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo ...)

[ http://issues.apache.org/jira/browse/DERBY-1819?page=all ] Suresh Thalamati updated DERBY-1819: Priority: Trivial (was: Major) couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo

Re: Options for syncing of log to disk

Knut Anders Hatlen wrote: Mike Matrigali [EMAIL PROTECTED] writes: I actually don't even know if we have ever run a set of tests on freebsd. I wonder if anyone in the comunity has tried out the 10.2 beta on feebsd? Just the results of a nightly test run would be interesting. I frequently

[jira] Commented: (DERBY-1783) Logical error in code for determining mode for opening of log files

[ http://issues.apache.org/jira/browse/DERBY-1783?page=comments#action_12432019 ] Suresh Thalamati commented on DERBY-1783: - Committted the patch (rwsyn.diff) to trunk, revision 439128. Thanks Olav, Logical error in code

[jira] Commented: (DERBY-1783) Logical error in code for determining mode for opening of log files

[ http://issues.apache.org/jira/browse/DERBY-1783?page=comments#action_12431642 ] Suresh Thalamati commented on DERBY-1783: - Good Catch Olav. I will review and commit the patch. Logical error in code for determining mode for opening

Re: Options for syncing of log to disk

Olav Sandstaa wrote: I have run some simple tests where I have changed mode from rws to rwd for the Derby log file. When running a small numbers of concurrent client threads the throughput is almost doubled and the response time is almost halved. I am enclosing two graphs that show this when

[jira] Created: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.

URL: http://issues.apache.org/jira/browse/DERBY-1786 Project: Derby Issue Type: Bug Affects Versions: 10.2.1.0, 10.3.0.0 Reporter: Suresh Thalamati Assigned To: Suresh Thalamati Attachments: stk.txt While running reencryt crash/recovery

[jira] Commented: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.

[ http://issues.apache.org/jira/browse/DERBY-1786?page=comments#action_12431756 ] Suresh Thalamati commented on DERBY-1786: - Hi Rick, This is related to new feature (re-encryption(DERBY-1156)). not a regression. User will hit

[jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12430617 ] Suresh Thalamati commented on DERBY-1636: - Thanks Laura, updates looks good. I reviewed both the reference manual and the developer guide changes. I have

[jira] Commented: (DERBY-803) derbynet/DerbyNetAutoStart.java test fails intermittently with org.apache.derby.iapi.services.context.ShutdownException

[ http://issues.apache.org/jira/browse/DERBY-803?page=comments#action_12430632 ] Suresh Thalamati commented on DERBY-803: This test is failing with a different error message also , might be related to the same issue

[jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12430662 ] Suresh Thalamati commented on DERBY-1636: - I reviewed the latest changes , they look good. Thanks a lot Laura. +1, this patch can be committed

[jira] Commented: (DERBY-1495) Attempt to modify an identity column error after resetting identity column

[ http://issues.apache.org/jira/browse/DERBY-1495?page=comments#action_12430083 ] Suresh Thalamati commented on DERBY-1495: - I came across this issue while doing a buddy testing for alter table with RESTART . It is really irritating

[jira] Commented: (DERBY-1685) The reference manual has wrong procedure name for online bacup

[ http://issues.apache.org/jira/browse/DERBY-1685?page=comments#action_12430061 ] Suresh Thalamati commented on DERBY-1685: - Good catch Jean,Bug description was incorrect.Correct version

[jira] Commented: (DERBY-1685) The reference manual has wrong procedure name for online bacup

[ http://issues.apache.org/jira/browse/DERBY-1685?page=comments#action_12430335 ] Suresh Thalamati commented on DERBY-1685: - +1 . This change can be committed. Whil reviewing this patch noticed BackupDir parameter description

Re: xalan assertion when execution a xml query...

Army wrote: Army wrote: Given the nature of the error Programmer's assertion in getNextStepPos, my guess is that this is a Xalan-side issue. For the record, I tried this with Xalan 2.7 and the assertion is gone; in its place is a much more reasonable exception: ij select

[jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12429839 ] Suresh Thalamati commented on DERBY-1636: - Thanks for explaining how the tasks are organized , Laura. I think what is needed is a new entry

xalan assertion when execution a xml query...

While doinng buddy testing of xml featuress, I think I gave a wrong xpath and XALAN throwed assertion to my surprise. Not sure if it is some setup issue from derby side or XALAN edge case bug. But annoying thing is after that query, it gives my favorite errror ERROR 40XT0: An internal

[jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12429141 ] Suresh Thalamati commented on DERBY-1636: - My understanding of it is; 1) users need to disable log archival then do a shutdown before attempting

[jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12429167 ] Suresh Thalamati commented on DERBY-1636: - Thanks for reviewing , sunitha. About u'r comments on FILE: cdevcsecure97760.html I like your idea about

[jira] Created: (DERBY-1718) creating an after insert trigger with trigger action involving xml datatype throws java.io.NottSerializableException

: http://issues.apache.org/jira/browse/DERBY-1718 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.2.2.0, 10.3.0.0 Environment: Java Version:1.4.2 Java Vendor: IBM Corporation Reporter: Suresh Thalamati

Re: [jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

Laura Stewart (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12428779 ] Laura Stewart commented on DERBY-1636: -- I have a concern about where the encryption information is located in the Developers

Re: DERBY-688: Is this a build problem? a CLASSPATH problem? a security problem?

Army wrote: Bryan Pendleton wrote: Hi Army, snip .. If you are just using the version that is part of Sun jdk 1.4.2, then I think there is a bug in that version of Xalan that is causing this error. I think it's related to XALANJ-1643 (type that in your Jira Quick Search box) and has

some minor doc warnings on the truk...

[javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\iapi\types\XML.java:262: warning - Tag @see: can't find setFrom org.apache.derby.iapi.types.DataValueDescriptor [javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\iapi\types\XML.java:163:

Re: [jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

Thanks for volunteering to document this Laura. Laura Stewart (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12428222 ] Laura Stewart commented on DERBY-1636: -- The spec indicates that the

Re: some minor doc warnings on the truk...

Army wrote: Suresh Thalamati wrote: [javadoc] C:\nightlies\main\src\opensource\java\engine\org\apache\derby\iapi\types\XML.java:262: warning - Tag @see: can't find setFrom org.apache.derby.iapi.types.DataValueDescriptor [javadoc] C:\nightlies\main\src\opensource\java\engine\org

[jira] Created: (DERBY-1702) lang/outparams.java and jdbcapi/parameterMapping.java fail on J9 ibm 131 jvm .

Platform API Specification java.specification.version: 1.3 Reporter: Suresh Thalamati Fix For: 10.2.2.0, 10.3.0.0 Attachments: outparams.diff, outparams.out, parameterMapping.diff diffs : Exception SQL Exception: No input parameters. 27a27 Exception

Re: [VOTE] Approve coding conventions for the Derby project

Kathey Marsden wrote: This is a vote to define the coding conventions for the Derby project per the db project guidelines http://db.apache.org/source.html Vote closes 10:00am, Wednesday, August 15. [+1] Adopt the coding convention described. [-1 ] Do not adopt the coding convention

What is the correct file to define new connection level attributes ?

As part of my (re) encryption work , added couple of new attributes newBootPassword and newEncryptionKey to org.apache.derby.iapi.reference.Attribute.java. today by accident noticed there is another version of Attribute.java in org.apache.derby.shared.common.reference What is correct file to

[jira] Commented: (DERBY-1667) Future Backups fails with ERROR XSRS4: Error renaming file after a consistency check is performed on the Backedup database

[ http://issues.apache.org/jira/browse/DERBY-1667?page=comments#action_12427347 ] Suresh Thalamati commented on DERBY-1667: - I think this is not a bug. In the above test case connection is made directly to backup copy

Re: Upcoming code convention vote (was Re: [jira] Commented: (DERBY-1363) Derby should publish a well defined coding convention per the db project guidlines)

Kathey Marsden wrote: Kathey Marsden wrote: snip .. Note: There is a great deal of existing code that does not match this convention. Changes to existing code should match the surrounding code for readability, matching tabs or spaces as appropriate (see Tabs) . Is it really necessary

[jira] Updated: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ] Suresh Thalamati updated DERBY-1636: Fix Version/s: 10.2.0.0 document encryption of an un-encrypted database and re-encryption with new password/key

[jira] Updated: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ] Suresh Thalamati updated DERBY-1636: Attachment: reencrypt_devgudechanges.txt Some thoughts on what should be documented in the developers guide for new feature that allows encryption

Re: adding permission to derby_tests.policy(was:Re: Using StorageFactory to create temporary files)

Anurag shekhar wrote: I need to grant derby.jar read,write,delete access on tmp directory (issue derby-1341). I tried adding permission java.io.FilePermission ${java.io.tmpdir}${/}-, read, write, delete; in this section grant codeBase ${derbyTesting.codejar}derby.jar I continue to get

Re: adding permission to derby_tests.policy(was:Re: Using StorageFactory to create temporary files)

Mike Matrigali wrote: Anurag Shekhar wrote: I can use database tmp file system. I can get the tmp directory name from StorageFactory. Or is there some better way of getting this directory ? anurag I don't think you should be using the database tmp file system for client code. You at

[jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Suresh Thalamati updated DERBY-1156: Attachment: reencrypt_6.diff DERBY -1156 (partial) (re) encryption of an existing database. This patch adds code required to correctly handle crash

[jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Suresh Thalamati updated DERBY-1156: Attachment: reencryptspec_1.html Minor updated to the spec. allow the encrypting of an existing unencrypted db and allow the re-encrypting

[jira] Created: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

Project: Derby Issue Type: Improvement Components: Documentation Affects Versions: 10.2.0.0 Reporter: Suresh Thalamati Attachments: reencryptspec_1.html document encryption of an un-encrypted database and re-encryption with new password/key

[jira] Updated: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ] Suresh Thalamati updated DERBY-1636: Attachment: reencryptspec_1.html document encryption of an un-encrypted database and re-encryption with new password/key

[jira] Commented: (DERBY-1636) document encryption of an un-encrypted database and re-encryption with new password/key.

[ http://issues.apache.org/jira/browse/DERBY-1636?page=comments#action_12425427 ] Suresh Thalamati commented on DERBY-1636: - Refence Guide Changes: 1) New Attributes doc for re-encryption newEncryptionKey

[jira] Assigned: (DERBY-1241) When booting a database under security manager, boot may fail with message java.sql.SQLException: Java exception: 'access denied (java.io.FilePermission for logmirro

[ http://issues.apache.org/jira/browse/DERBY-1241?page=all ] Suresh Thalamati reassigned DERBY-1241: --- Assignee: (was: Suresh Thalamati) fix might be simple one line chage of calling file.exists on mirror control file in the privileged

[jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Suresh Thalamati updated DERBY-1156: Attachment: reencrypt_5.diff DERBY -1156 (partial) re-encryption of the database. This patch adds a new test that tests recovery of the database

Re: Hard upgrade issues for 10.2

Rick Hillegas wrote: GRANT/REVOKE requires catalog support and so won't be available to users who soft-upgrade to 10.2. Are there other 10.2 features which will not be available after soft upgrade? Thanks, -Rick yes. 1) Two new procedure that are added as part of real-time online backup

[jira] Commented: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=comments#action_12422263 ] Suresh Thalamati commented on DERBY-1373: - I reviewed the patch , it looks good. Thanks for adding the test to test the encryption with jar

[jira] Commented: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=comments#action_12422304 ] Suresh Thalamati commented on DERBY-1373: - Committed derby1373.diff.txt patch to trunk with revision 423682. Encrypted databases cannot be booted

[jira] Commented: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=comments#action_12422000 ] Suresh Thalamati commented on DERBY-1156: - How to handle crash/recovery when switching to new encryption key ? After re-encrypting all the containers

[jira] Commented: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=comments#action_12422009 ] Suresh Thalamati commented on DERBY-1373: - I am planning to review/commit derby1373.diff.txt patch, if any one else is reviewing this patch, please

[jira] Commented: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=comments#action_12420960 ] Suresh Thalamati commented on DERBY-1156: - FIixed the comments as suggected by Mike, and committed reencrypt_4.diff patch to trunk with revision 421721. allow

[jira] Commented: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=comments#action_12420699 ] Suresh Thalamati commented on DERBY-1156: - Committed reencrypt_3.diff patch to trunk with revision 416536 allow the encrypting of an existing unencrypted db

[jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Suresh Thalamati updated DERBY-1156: Attachment: reencrypt_4.diff DERBY -1156 (partial) This patch adds some code required to support reconfigure(rencryption) of an already existing

[jira] Closed: (DERBY-1045) forupdate.sql , holdCursorIJ.sql ..etc are failing when run with 10.1 client againest trunk

[ http://issues.apache.org/jira/browse/DERBY-1045?page=all ] Suresh Thalamati closed DERBY-1045: --- forupdate.sql , holdCursorIJ.sql ..etc are failing when run with 10.1 client againest trunk

[jira] Closed: (DERBY-437) SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names.

[ http://issues.apache.org/jira/browse/DERBY-437?page=all ] Suresh Thalamati closed DERBY-437: -- SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with delimited identifier names

[jira] Closed: (DERBY-523) Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.

[ http://issues.apache.org/jira/browse/DERBY-523?page=all ] Suresh Thalamati closed DERBY-523: -- Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery

[jira] Closed: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati closed DERBY-239: -- Need a online backup feature that does not block update operations when online backup is in progress

[jira] Closed: (DERBY-758) CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions.

[ http://issues.apache.org/jira/browse/DERBY-758?page=all ] Suresh Thalamati closed DERBY-758: -- CachedPage.readPage() can loop forever on insane builds if the read from the container keep failing with IO Exceptions

Re: Can I encrypt a non encrypted database ?

Kristian Waagan wrote: Supal J Patel wrote: Hi, If I have a database which is not encrypted and have some data in it , can I now encrypt that database ? In all the manuals they talk abt how to create a new encrypted database. Its no where mentioned that if you can or can not encrypt

[jira] Commented: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=comments#action_12419356 ] Suresh Thalamati commented on DERBY-989: Hi Knut, Thanks for looking into this failure. I took a quick look at your changes,patch looks good. Only minor thing I

[jira] Commented: (DERBY-1460) Instability in storerecovery suite when run against jar files on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-1460?page=comments#action_12418127 ] Suresh Thalamati commented on DERBY-1460: - Hi Rick, If you still have the test directory for this failure , could you please attach it the to the jira entry

Re: Wrapping up coding for 10.2

Rick Hillegas wrote: I hate to be a nudge, but I didn't get a response when I asked this question last week: Do we expect to be done with development for 10.2 by August 10? I expect that the JDBC4 work will have wrapped up by then. Besides the JDBC4 effort, 10.2 is waiting for feature work

Re: [VOTE] 10.1.3.0 release

Mike Matrigali wrote: I would like to see the fix for DERBY-1392 included in the 10.1.3 release if there is a second release candidate. While the bug is an edge error case, the result is a corrupt db. I believe there is little risk as again the path is not one usually taken. The change has

Re: [jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

Mike Matrigali (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Mike Matrigali updated DERBY-1156: -- i reviewed and tested reencrypt_3.diff patch. it looks fine, i will let you commit. Still would like to see more testing,

[jira] Commented: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

[ http://issues.apache.org/jira/browse/DERBY-1435?page=comments#action_12417226 ] Suresh Thalamati commented on DERBY-1435: - Good catch deepa. My guess is the plans in the statement cache are not getting invalidated corretcly when table t1

[jira] Updated: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

[ http://issues.apache.org/jira/browse/DERBY-1435?page=all ] Suresh Thalamati updated DERBY-1435: Component: SQL (was: Store) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

[jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Suresh Thalamati updated DERBY-1156: Attachment: reencrypt_3.diff DERBY -1156 (partial) This patch adds some code required to support reconfigure(rencryption) of an already existing

[jira] Assigned: (DERBY-1241) logmirror.ctrl is getting accessed outside the privileged block when the checkpoint instant is invalid on log factory boot method.

[ http://issues.apache.org/jira/browse/DERBY-1241?page=all ] Suresh Thalamati reassigned DERBY-1241: --- Assign To: Suresh Thalamati logmirror.ctrl is getting accessed outside the privileged block when the checkpoint instant is invalid on log

Re: Driver autoloading and engine booting

Rick Hillegas wrote: This topic was raised in an earlier email thread (http://comments.gmane.org/gmane.comp.apache.db.derby.devel/20899) but it does not appear that we agreed on a solution. I would like to re-open this topic and hopefully we can converge on how we want to handle this issue.

<    1   2   3   4   5   6   >