a backup.
Suresh Thalamati wrote:
Thanks for taking time to review. My comments are in-line for some
of the questions, I will respond to the other questions in another
e-mail.
From you comments, one issue that we are uable to come to conclusion,
is what to do if a backup call is issued
Øystein Grøvlen wrote:
ST == Suresh Thalamati [EMAIL PROTECTED] writes:
ST Thanks for taking time to review. My comments are in-line for some
ST of the questions, I will respond to the other questions in another
ST e-mail.
ST From you comments, one issue that we
.
Key: DERBY-239
URL: http://issues.apache.org/jira/browse/DERBY-239
Project: Derby
Type: New Feature
Components: Store
Versions: 10.1.1.0
Reporter: Suresh Thalamati
Assignee: Suresh
Øystein Grøvlen wrote:
Suresh,
Just a reminder of some things you promised to fix in the previous
review round.
Thanks for reminding. It is on my list. Just thought I can do the
cleanup after I fix the major issues to make online backup work
correctly.
Thanks
-suresh
.
Key: DERBY-239
URL: http://issues.apache.org/jira/browse/DERBY-239
Project: Derby
Type: New Feature
Components: Store
Versions: 10.1.1.0
Reporter: Suresh Thalamati
Assignee
[
http://issues.apache.org/jira/browse/DERBY-298?page=comments#action_12361808 ]
Suresh Thalamati commented on DERBY-298:
Øystein ,
I reviewed the latest patch, it looks good. But I could not understand why
you would need the following check
Hi Rick ,
you may also want to check if import/export works fine with the
BOOLEAN data type, i u have not already done.
Thanks
-suresh
Daniel John Debrunner (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12361007 ]
Daniel John Debrunner commented
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup_6.diff
This patch adds code to support online backup when jar operations
are running parallel to the backup. Jar files
This might be obvious, thought I would mention it any way. My
understanding is one can not just enable RWD (direct io) for the
checkpoint. It has to be enabled for all the writes from the page
cache, otherwise a file sync is required before doing rwd writes
because I am not sure If a file is
Hi Knut,
I am really puzzled with such a large differene in response
times between the jdk142 and jdk15 jvms. Did u find out what has
changed in jdk15 that is making the response time so bad ?
Sun JVM 1.4.2: 78.3 tps /727 ms max resp
Sun JVM 1.5.0: 78.2 tps / 609483 ms max
[ http://issues.apache.org/jira/browse/DERBY-750?page=all ]
Suresh Thalamati updated DERBY-750:
---
Attachment: obtest1.diff
Thanks for posting the stack Ole. By looking at the stacks , my suspicion is
backup is looking at a table
for the new test.
Suresh Thalamati (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup_6.diff
This patch adds code to support online backup when jar operations are
running
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: obtest_customer.jar
test jar file was missing from the earlier onlinebackup_6.diff patch. This
jar file should be added to :
org/apache
Type: Bug
Reporter: Suresh Thalamati
Priority: Minor
Found one Java-level deadlock:
=
Thread-2:
waiting to lock monitor 0x00a8872c (object 0x03002be8, a org.apache.derby.impl
.services.locks.LockSet),
which is held by Thread-0
Thread-0:
waiting
://issues.apache.org/jira/browse/DERBY-757
Project: Derby
Type: Bug
Components: Store
Versions: 10.2.0.0, 10.1.3.0, 10.1.2.2, 10.0.2.2
Reporter: Suresh Thalamati
TransactonTable.java:
public ContextManager findTransactionContextByGlobalId(
if (entry.getGid() != null
[ http://issues.apache.org/jira/browse/DERBY-750?page=all ]
Suresh Thalamati reassigned DERBY-750:
--
Assign To: Suresh Thalamati
OnlineBackupTest1.java intermittently hangs
---
Key: DERBY-750
[
http://issues.apache.org/jira/browse/DERBY-750?page=comments#action_12360233 ]
Suresh Thalamati commented on DERBY-750:
If some one sees this test hang, please post the stack dump. It does not
reproduce on my linux/windows envirorments
Following error is interesting :
java.lang.ClassCastException: org.apache.derby.iapi.store.raw.PageKey
By chance did u change the derby jar files when the system is running
or are there two versions of derby jars in the classpath ?
Thanks
-suresht
Thomas Feldmann (JIRA) wrote:
Currupt
Thanks for reporting the failure. I added this test with my last
online backup patch, I will look into it, might be timing issue with
the test.
Thanks
-suresh
Ole Solberg wrote:
Checking regression test logs I observe that *since svn 345370*
derbyall, storemore and storeall reports *error
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup_4.diff
This patch makes online backup call to wait/fail when unlogged operations like
create index are pending. It also fixes
lang/dcl.sql is failing with following error message in my clients.
From the message looks , jar signing expired or some thing like that.
Any one else seeing this failure or my client is messed up ?
ERROR 42X51: The class
'org.apache.derbyTesting.databaseclassloader.emc' does
not exist or is
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup1.html
minor updates to the spec:
- Procedure can not be overloaded with different number of arguments in
Derby. Added
There was one bug in this area ( Derby-32) in the first version of
Derby (10.0 I think). What is the Derby version and the OS are you
using ?
Other than that bug, this error occurs only when some one boots derby
db through multiple jvms/different class loaders in the same jvm at
the same
[
http://issues.apache.org/jira/browse/DERBY-720?page=comments#action_12358036 ]
Suresh Thalamati commented on DERBY-720:
derby-365 might be a duplicate of this issue.
Calling SYSCS_INPLACE_COMPRESS_TABLE on a synonym or a temp table results
Mike Matrigali wrote:
I have tested this patch and reviewed the changes and
have commited it as svn 345355.
I have the following
suggestions from review, and will look at any subsequent
changes in these areas that Suresh would like to submit:
o RawStore.java!canStartOnlineBackup() has a todo
[ http://issues.apache.org/jira/browse/DERBY-523?page=all ]
Suresh Thalamati reassigned DERBY-523:
--
Assign To: Suresh Thalamati
Non logged operation that starts before the log archive mode is enabled can
not be recovered during rollforward
Rick Hillegas wrote:
Is anyone planning to fix bug 523 as part of the 10.2 release? This is a
high priority bug having to do with log archive and rollforward recovery.
Thanks,
-Rick
Yes. I will fix it for 10.2, my last patch on derby-239 addresses this
problem also.
Thanks
-suresht
Øystein Grøvlen wrote:
MM == Mike Matrigali [EMAIL PROTECTED] writes:
MM It is only stable while some sort of stable table intent lock is held.
MM Rows can move during a compress table operation.
I understand, when a record is moved to another page, its RecordId
will change. Is this
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup_3.diff
This patch adds code to support real-time online backup with unlogged
operations. A consistent backup can not be made
Andreas Korneliussen wrote:
Mike Matrigali wrote:
snip
I would think there are multiple ways of adressing this issue:
1 We could make the store graciously handle the situation if the
RowLocation points to a deleted+purged row, by returning false if the
RowLocation is invalid, (and from
I think the scope of file lock is for the whole JVM , not specific to
a class loader. This is what I found in the java doc for
java.nio.channels.FileChannel.tryLock() that is used by the Derby.
File locks are held on behalf of the entire Java virtual machine.
They are not suitable for
[
http://issues.apache.org/jira/browse/DERBY-700?page=comments#action_12357312 ]
Suresh Thalamati commented on DERBY-700:
My guess is , currently Derby seems to catch the IO exception and turn it into
a readonly db , when file lock fails
Hi Daniel,
Assert failures are not good for sure. My guess is, in some case
the release of a cached item is getting called more than once. In a
rare scenario it is possible that this can cause the item to be
cleaned from cache even if some one else is using it.
I don't know how serious this
[
http://issues.apache.org/jira/browse/DERBY-685?page=comments#action_12356975 ]
Suresh Thalamati commented on DERBY-685:
Thanks for posting the complete stack trace. By looking at the stack and
related code in Logtofile.java , it appears to me
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup_2.diff
Fix to the problem found by Øystein while reviewing the previous online
backup patch(online_backup1.diff).
Backup
Thanks for the input. I will go with the option 1.
Nested transaction may not solve this problem , Nested Transaction
will be be on the same thread as the user thread, so user will not be
able to commit the unlogged operations for the backup operation to
proceed.
Thanks
-suresht
Øystein
Øystein Grøvlen wrote:
ST == Suresh Thalamati [EMAIL PROTECTED] writes:
ST Hi Øystein,
ST Thanks for reviewing the patch. My answers are in-line...
ST Øystein Grøvlen (JIRA) wrote:
snip ...
ST By using the catalog approach also backup can only throw a warning
ST
[
http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12356240 ]
Suresh Thalamati commented on DERBY-239:
What to do if backup is started in a transaction that already has unlogged
operations executed?
In previous discussions
Daniel John Debrunner wrote:
When running storeunit with the security manager, I'm down to only one
failure, T_RecoverFullLog. It passes for me without the security
manager, fails with, but not due to a security exception.
My guess is that somewhere some system properties are not being set or
Colin Rosenthal wrote:
On Tue, 2005-10-25 at 13:30, Knut Anders Hatlen wrote:
Colin Rosenthal [EMAIL PROTECTED] writes:
Hi all,
We have an application which uses derby in auto-commit=false mode.
For some reason a row in one of our tables cannot be updated from
our system. Attempting to do
duschhaube wrote:
Hi!
Is it possible to use regular expressions in a select statement.
for example select * from test where name=a*b
ciao
I don't think you can do that way. Using the like operator, one can
do some pattern matching in Derby.
For Example:
create table t2(name char(30)
Hi Øystein,
Thanks for reviewing the patch. My answers are in-line...
Øystein Grøvlen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12355620 ]
Øystein Grøvlen commented on DERBY-239:
---
I have looked at the
files are OK. I am currently reviewing your code, and I
have already seen that you handle the log copying correctly there.
--
Øystein
ST == Suresh Thalamati [EMAIL PROTECTED] writes:
ST Øystein Grøvlen wrote:
ST( == Suresh Thalamati (JIRA) derby-dev@db.apache.org writes
[
http://issues.apache.org/jira/browse/DERBY-1?page=comments#action_12331723 ]
Suresh Thalamati commented on DERBY-1:
--
Merged this fix into 10.1 client from trunk and ran all functional tests. All
tests passes on jdk142/WindowsXP.
I like to see
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup_1.diff
This patch adds some code necessary to support real-time online backup that
does not block writes when database backup
$ svn log
Authentication realm: https://svn.apache.org:443 ASF Committers
Password for 'suresht':
This used to work fine for me till yesterday.
Thanks
-suresh
Daniel John Debrunner wrote:
David W. Van Couvering wrote:
Another candidate for the Wiki site?
The functional spec should at least be attached to the Jira entry.
Dan.
Good point, will attach it to the jira for the moment. Have not
figured out yet, how Wiki works.
Thanks
-suresh
[ http://issues.apache.org/jira/browse/DERBY-239?page=all ]
Suresh Thalamati updated DERBY-239:
---
Attachment: onlinebackup.html
functional/design spec based on the input I got on the derby-dev list.
Need a online backup feature that does not block
Attached is the functional/design spec based on the input I got from
everyone on this topic. I think, most of the issues are covered in
this doc, except the backup of jars stored inside the database.
Thanks
-suresh
Title: Online Backup
Online Backup Functional/Design Spec
[
http://issues.apache.org/jira/browse/DERBY-1?page=comments#action_12331234 ]
Suresh Thalamati commented on DERBY-1:
--
I was hoping this issue will go away , but it seems to have appeared again in
jdk1.5. Although there is a workaround by
setting
[
http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12330529 ]
Suresh Thalamati commented on DERBY-555:
Hi Øystein,
Tested your patch , it looks good .I have couple of minor questions,
related to the new error message
: Derby
Type: Improvement
Components: Test
Reporter: Suresh Thalamati
Priority: Minor
If the user.dir property is changed , you wil find IO calls are working on
different directory than what is returned by
File.getAbsolutePath() if the file handle is created
[
http://issues.apache.org/jira/browse/DERBY-151?page=comments#action_12329329 ]
Suresh Thalamati commented on DERBY-151:
derby.log occasional has more information than the above stack mentioned. In
most cases , some sort of IO exception has
[
http://issues.apache.org/jira/browse/DERBY-151?page=comments#action_12329341 ]
Suresh Thalamati commented on DERBY-151:
Real cause for the error(ERROR XSDG1: Page Page(7,Container(0, 1088)) could not
be written to disk, please check if disk
Scotty Allen wrote:
Suresh Thalamati wrote:
snip ..
Nope, these errors are from my personal laptop, and I haven't touched
any of the files in the data directories. I did run a test whereby I
killed the java process that was running the application, and then
deleted log1.dat manually
[
http://issues.apache.org/jira/browse/DERBY-555?page=comments#action_12320936 ]
Suresh Thalamati commented on DERBY-555:
One case I can think of database disk is full and system is unable to create
even a lock (db.lck) file also. In derby
[ http://issues.apache.org/jira/browse/DERBY-437?page=all ]
Suresh Thalamati resolved DERBY-437:
Resolution: Fixed
Mike committed patch for this problem : sv n : r219207
SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables
: Improvement
Components: Store
Versions: 10.1.1.1
Reporter: Suresh Thalamati
During log file switch , the logging system blocks all the writes to the
transaction log. One of the tasks during
log switch is preallocation. By doing preallocation without blocking the
log writes might
://issues.apache.org/jira/browse/DERBY-523
Project: Derby
Type: Bug
Components: Store
Reporter: Suresh Thalamati
once the log archive mode that is required for roll-forward recoveryis enabled
all the operations are logged including the operations that are not logged
normally like
/browse/DERBY-524
Project: Derby
Type: New Feature
Components: Services
Versions: 10.1.1.1
Reporter: Suresh Thalamati
This issue was discussed on the derby-dev list along with online backup
(derby-239) design , because online backup will read pages into the cache
description of the steps I am following to
close the database,
1 Close all the statements and prepared statements.
2 Shutdown the database
are u closing the result sets ?
Can you please let me know, whether there should be something more that
I should do?
Regards:
Amit Modi
Suresh Thalamati
Hi Amit,
If you are just closing the connections, some of the memory used by
the database internal structures will not be released,for example
memory used by the page cache will not be released; default size of
cache is 1000 pages, if cache is full, it can take up 32MB if all
pages are 32K or
Bai Xiaoguang wrote:
I am going to do something for the Dynamic swap of derby.log(there are
some comments for Dynamic), so anyone can give me some ideas or suggestions?
And where I can get some documentations talk about what derby does now?
derby.log is the default error/status log file.
The stack in derby.log is interesting , I do see a run() method in
RafContainer.java.
1) Are u running under security manager ?
2) What JVM OS are u using ?
3) Are u able to reproduce this problem with a simple set of SQL
statements not the whole application ?
Could u please post the
Actually it is not a bug , that is the expected behavior in version
10.1 after derby-390 fix. table name in the following should be
passed in upper case as TEST1 to the import procedure.
After the derby-390 fix with 208770 patch you mentioned, If you create
a schema, table, or column name
+1
Rick Hillegas wrote:
I propose to close bug 499 by re-enabling the ANSI-SQL standard BOOLEAN
datatype which was disabled before IBM open-sourced Derby.
A yes vote means that you want to re-enable the ANSI-SQL standard
BOOLEAN datatype.
A no vote means that you do NOT want Derby to
Kathey Marsden wrote:
Army wrote:
[snip , lots of good comments ]
4) From what I can tell, the changes to refActions1.out fall into four
categories:
a -- update/delete statements that used to throw syntax errors
because of DERBY-171 were left unchanged but now run without error.
Ex. see
in parallel to the
data files copy operation. I also think, this enhancement is not
essential for first implementation of real time online backup.
Thanks
-suresht
Øystein Grøvlen wrote:
ØG == Øystein Grøvlen [EMAIL PROTECTED] writes:
ST == Suresh Thalamati [EMAIL PROTECTED] writes
Hi Matt ,
I came across this error only when the disk is full or when there are
file system errors. Surprised to find that you don't see log flush
SQL Exception in the derby.log. May be the error log is getting
reinitialized when you reboot after a shutdown inside your program.
You
Øystein Grøvlen wrote:
ST == Suresh Thalamati [EMAIL PROTECTED] writes:
.snip
ST I agree it by writing log record for start of backup, we can prevent
ST garbage-collection of log files.
ST My initial thought is to simply disable garbage-collection of log
Suresh Thalamati wrote:
Øystein Grøvlen wrote:
ST == Suresh Thalamati [EMAIL PROTECTED] writes:
.snip
ST I agree it by writing log record for start of backup, we can
prevent
ST garbage-collection of log files.
ST My initial thought is to simply disable
Thanks for the input , Øystein. My comments are in-line.
Øystein Grøvlen wrote:
Øystein
ST( == Suresh Thalamati (JIRA) derby-dev@db.apache.org writes:
ST( Currently backup contains mainly data files (seg0/*) and the
ST( transaction log files(log
Daniel John Debrunner wrote:
Suresh Thalamati (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12316434 ]
Suresh Thalamati commented on DERBY-239:
[comments just on this issue]
b) read each pages
[
http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12316434 ]
Suresh Thalamati commented on DERBY-239:
I think providing an online backup mechanism that does not block changes
to the database when the backup is in progress
[
http://issues.apache.org/jira/browse/DERBY-426?page=comments#action_12316168 ]
Suresh Thalamati commented on DERBY-426:
Changes looks good.
documentation need to be modified to reflect the derby-390 fix(once it is
committed) , schem , table
[
http://issues.apache.org/jira/browse/DERBY-426?page=comments#action_12315960 ]
Suresh Thalamati commented on DERBY-426:
Thanks for making the changes Jeff, Changes are good , except for the
following minor error:
Export procedures does
[ http://issues.apache.org/jira/browse/DERBY-390?page=all ]
Suresh Thalamati resolved DERBY-390:
Fix Version: 10.1.1.0
10.2.0.0
Resolution: Fixed
patch was committed to 10.1 branch wiith svn 208776
patch was committed
[
http://issues.apache.org/jira/browse/DERBY-426?page=comments#action_12315649 ]
Suresh Thalamati commented on DERBY-426:
Fix for Derby-390 , that required the suggested doc change in this bug is
committed to 10.1 branch. It woud be great
+1
Daniel John Debrunner wrote:
Please vote on making David a committer on the Derby project. The
derby-ppmc believe David will be a great benefit to Derby.
[ ] - Add David Van Couvering [EMAIL PROTECTED] as a Derby
committer
---
My vote: +1
Dan.
[ http://issues.apache.org/jira/browse/DERBY-437?page=all ]
Suresh Thalamati reassigned DERBY-437:
--
Assign To: Suresh Thalamati
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 updated DERBY-437:
---
Attachment: derby437.diff
Currently for compress procedure to work incase of case-sensitive table name ,
schema names, they needs to be passed in quotes
[
http://issues.apache.org/jira/browse/DERBY-298?page=comments#action_12315265 ]
Suresh Thalamati commented on DERBY-298:
Hi Øystein,
I could not understand from the changes, If the new log file will be
recognized in the following two cases
+1
Daniel John Debrunner wrote:
Please vote on making Bernt a committer on the Derby project. The
derby-ppmc believe Bernt will be a great benefit to Derby.
[ ] - Add Bernt M. Johnsen [EMAIL PROTECTED] as a Derby committer
---
My vote: +1
Dan.
Daniel John Debrunner wrote:
Please vote on making Øyvind a committer on the Derby project. The
derby-ppmc believe Øyvind will be a great benefit to Derby.
[ ] - Add Øyvind Bakksjø [EMAIL PROTECTED] as a Derby committer
---
My vote: +1
Dan.
+1
-suresh
-437
Project: Derby
Type: Bug
Components: SQL
Versions: 10.0.2.2
Reporter: Suresh Thalamati
Fix For: 10.2.0.0
COMPRESS_TABLE procedure forms SQL statement undeneath, so if the user does
not pass quoted names , it is not working with delimited table/schema names
[ http://issues.apache.org/jira/browse/DERBY-390?page=all ]
Suresh Thalamati updated DERBY-390:
---
Attachment: derby390.diff
patch to handle case-sensitive SQL identifiers correctly. Import/export
procedure parameters for
table names , schema
[
http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314825 ]
Suresh Thalamati commented on DERBY-377:
Looks good to me.I am not sure of the following statements , In the
Upgrades section ,
whether on upgrade from 10.0
.
---
Key: DERBY-426
URL: http://issues.apache.org/jira/browse/DERBY-426
Project: Derby
Type: Sub-task
Components: Documentation
Versions: 10.1.1.0
Reporter: Suresh Thalamati
Tools utilities Guide: Using bulk import/export chapter:
BulkImport
[
http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314842 ]
Suresh Thalamati commented on DERBY-390:
Same patch (derby390.diff) also works fine for 10.1 branch also. Ran Derbyall
on 10.1 after applying the patch for a 10.1
[ http://issues.apache.org/jira/browse/DERBY-390?page=all ]
Suresh Thalamati reassigned DERBY-390:
--
Assign To: Suresh Thalamati
Import/export fails with table names that are quoted in SQL like import
to table Order
[
http://issues.apache.org/jira/browse/DERBY-367?page=comments#action_12314634 ]
Suresh Thalamati commented on DERBY-367:
It might be good idea to mention about this new procedure in Server/Admin
Guide: Reclaiming unused space: Chapter
[
http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314415 ]
Suresh Thalamati commented on DERBY-390:
By looking at other system procedures and the way JDBC methods takes the
table names,it looks like following the second
Type: Bug
Versions: 10.0.2.1
Reporter: Suresh Thalamati
import fails irrespective off whether the name is passed as a quoted
sttring or not:
ij call SYSCS_UTIL.SYSCS_IMPORT_TABLE (null, 'ORDER' , 'order.dat' ,
null, null, null, 0) ;
ERROR
() call...you might want to do this if you want to
ensure you are dealing with a valid table satisfying your search
before returning the columns...
Just some thoughts...
--francois
On 6/22/05, Suresh Thalamati [EMAIL PROTECTED] wrote:
I have a table that uses reserved word as name , so
[
http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314344 ]
Suresh Thalamati commented on DERBY-390:
There are two ways to fix this problem:
1) Import/Export should treat schema Names , table Names , Column Names
the table name and build a query which it then
sends back to the parser?
Suresh Thalamati wrote:
Thanks Francois, your explanation was realy helpful.
-suresh
Francois Orsini wrote:
The quotes are there for the parser to treat the table object
(ansi-92) identifier as case sensitive
I have a table that uses reserved word as name , so it is quoted like :
create table ORDER(a int ) ;
All SQL queries seems to expect it as quoted name , except Database
Metadata getColumns(..).
DatabaseMetaData dmd = conn.getMetaData();
ResultSet rs = dmd.getColumns(null, null , \ORDER\ ,
Please add me to the list.
Thanks
-suresht
David Van Couvering wrote:
Hi, all. I suspect my request for RSVP may have been lost in the high
volume of email on this list, so I thought I would try a more
attention-getting subject.
So far I have confirmed for our lunch at noon on Tuesday
/DERBY-377
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.1.0
Reporter: Suresh Thalamati
Fix For: 10.1.1.0
I could not find any info in the 10.1 Alpha manuals on how to upgrade a
10.0 database to use
a 10.1 engine in full upgrade mode
://issues.apache.org/jira/browse/DERBY-378
Project: Derby
Type: Improvement
Components: Tools
Versions: 10.1.1.0
Reporter: Suresh Thalamati
Currently if I have a table that contains clob/blob column, import/export
operations on that table
throghs unsupported feature
401 - 500 of 578 matches
Mail list logo
