[ http://issues.apache.org/jira/browse/DERBY-1653?page=all ]
Andrew McIntyre updated DERBY-1653:
---
Component/s: Store
> Database gets corrupt after throwing NPE while reading Binary Stream data, in
> chunks
> ---
[ http://issues.apache.org/jira/browse/DERBY-1629?page=all ]
Andrew McIntyre updated DERBY-1629:
---
Component/s: JDBC
SQL
> Exceptions thrown by code in procedures or triggers are not handled/thrown
> correctly by Derby
> --
[ http://issues.apache.org/jira/browse/DERBY-1669?page=all ]
Andrew McIntyre updated DERBY-1669:
---
Component/s: JDBC
> DatabaseMetaData.getIndexInfo() does not differentiate between generated and
> real indexes
> ---
[ http://issues.apache.org/jira/browse/DERBY-1627?page=all ]
Andrew McIntyre updated DERBY-1627:
---
Component/s: Test
> Need a regression test for DERBY-1241
> -
>
> Key: DERBY-1627
> UR
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
Andrew McIntyre updated DERBY-1659:
---
Component/s: Documentation
> Document describe and show tables functionality
> ---
>
> Key: DE
[ http://issues.apache.org/jira/browse/DERBY-1569?page=all ]
Andrew McIntyre updated DERBY-1569:
---
Component/s: Test
> analyze 10.1 tests with 10.2 derby to determine which Jira fixes in 10.2 may
> have existing application impact
> --
[ http://issues.apache.org/jira/browse/DERBY-1485?page=all ]
Andrew McIntyre resolved DERBY-1485.
Resolution: Fixed
Committed to 10.1 branch with revision 430539.
> Document that autoflush is needed if Network Server is started with a
> PrintWriter
[ http://issues.apache.org/jira/browse/DERBY-950?page=all ]
Andrew McIntyre updated DERBY-950:
--
Fix Version/s: 10.3.0.0
(was: 10.2.0.0)
Pushing to 10.3. Issue might need to be closed due to recent push for JUnit
tests.
> Add inf
[ http://issues.apache.org/jira/browse/DERBY-667?page=all ]
Andrew McIntyre updated DERBY-667:
--
Fix Version/s: 10.3.0.0
(was: 10.2.0.0)
Pushing to 10.3, since /bin scripts are pending, and there's no clear plan for
how to test an
[ http://issues.apache.org/jira/browse/DERBY-221?page=all ]
Andrew McIntyre updated DERBY-221:
--
Fix Version/s: 10.3.0.0
(was: 10.2.0.0)
Pushing out to 10.3 as this is not urgent.
> User documentation should include a timestamp an
[ http://issues.apache.org/jira/browse/DERBY-1618?page=all ]
Andrew McIntyre updated DERBY-1618:
---
Component/s: Regression Test Failure
> store/BootAllTest.junit fails on ibm131, wctme5.7
> -
>
>
[ http://issues.apache.org/jira/browse/DERBY-1606?page=all ]
Andrew McIntyre updated DERBY-1606:
---
Component/s: Test
> derbyrunjartest hangs with wctme5.7 & always uses j9_13; hangs with
> _foundation
> -
[ http://issues.apache.org/jira/browse/DERBY-1591?page=all ]
Andrew McIntyre resolved DERBY-1591.
Resolution: Fixed
Marking as resolved, since the code coverage results at:
http://people.apache.org/~fuzzylogic/codecoverage/428586/
include JDBC 4.0
[
http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12427430 ]
A B commented on DERBY-688:
---
> Committed d688_patch4_v2.patch to subversion as revision 430626
> patch d688_patch_v5.txt committed to subversion as revision 430670.
I sy
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427428 ]
Jorg Janke commented on DERBY-1577:
---
Yes DERBY-543 is basically the same - my suggestion would to use the same name
for the index as for the constraint. But, tha
[ http://issues.apache.org/jira/browse/DERBY-1597?page=all ]
Andrew McIntyre resolved DERBY-1597.
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed to trunk with revision 430681.
> Scripts in frameworks direcotry needs to be rev
[
http://issues.apache.org/jira/browse/DERBY-1597?page=comments#action_12427424 ]
Andrew McIntyre commented on DERBY-1597:
I retract the previous comment, the patch as-is provides the same behavior as
today without the need to call the s
[
http://issues.apache.org/jira/browse/DERBY-1032?page=comments#action_12427419 ]
Andrew McIntyre commented on DERBY-1032:
Committed derby-1032-v2.diff to trunk with revision 430668 (unix scripts) and
430677 (windows scripts). Two commit
[ http://issues.apache.org/jira/browse/DERBY-688?page=all ]
Bryan Pendleton updated DERBY-688:
--
Derby Info: (was: [Patch Available])
patch d688_patch_v5.txt committed to subversion as revision 430670.
Clearing patch_available as all pending patches h
[ http://issues.apache.org/jira/browse/DERBY-1593?page=all ]
Andrew McIntyre updated DERBY-1593:
---
Derby Info: [Patch Available]
> Separate test jar files from the "product" jars in a distribution
> --
[ http://issues.apache.org/jira/browse/DERBY-1593?page=all ]
Andrew McIntyre updated DERBY-1593:
---
Attachment: derby-1593-v1.diff
Simple patch which moves derbyTesting.jar into a top-level test directory in
the -bin, -lib, and -lib-debug distributions.
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427409 ]
Daniel John Debrunner commented on DERBY-1577:
--
Is this the same issue as DERBY-543?
DatabaseMetaData.getIndexInfo provides misleading/confusing inform
[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ]
Kathey Marsden updated DERBY-1130:
--
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Patch Available])
Thanks Deepa for the patch and Sunitha for the review.
I checked
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427405 ]
Kathey Marsden commented on DERBY-1577:
---
Thanks Jorg,
I am glad you were able to find a solution for your application. Would it be ok
to close out this issu
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427392 ]
Jorg Janke commented on DERBY-1577:
---
A work-around is to use DatabaseMetaData.getPrimaryKeys().
The cause is that in most database systems, the constraint name is
DatabaseMetaData.getIndexInfo() does not differentiate between generated and
real indexes
-
Key: DERBY-1669
URL: http://issues.apache.org/jira/browse/DERBY-1669
P
[
http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12427391 ]
Bryan Pendleton commented on DERBY-688:
---
Committed d688_patch4_v2.patch to subversion as revision 430626
> Enhancements to XML functionality to move toward X
David Van Couvering <[EMAIL PROTECTED]> writes:
> Oh, one more thing, the database I have heard us compared with is
> HSQL. Folks don't expect us to be equivalent, given that HSQL is
> in-memory, but they do complain that the difference is just a little
> too much, from basically instantaneous to
Yip Ng <[EMAIL PROTECTED]> writes:
> Appreciated it if someone can find some time to review DERBY-1652.
I will review at this tomorrow.
Dag
On 8/10/06, Kathey Marsden <[EMAIL PROTECTED]> wrote:
That's what I had to do but it sure would be good to get those targets
fixed up if you can figure out what's going on.
I don't think its the way the targets are written, I think gpg + Ant +
Windows just don't play nice together. The targets
[
http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12427386 ]
Kathey Marsden commented on DERBY-1564:
---
Thanks John for investigating this issue. If you have the wisconsin.java test
ported to 10.1 and have a patch, I wi
Andrew McIntyre wrote:
Kathey reported this as well, I think Ant on Windows won't print the
gpg password prompt. You could try typing your password in eight time.
I'd recommend you save your sanity and don't go there.
Or just sign the jars using the script at the end of #11 on the
Snapshot
On 8/10/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
I'm seeing the following behavior when running the "ant sign" target
from tools/release. I'm running on cygwin. Would appreciate advice.
md5.options=-n
It would be good to note that this is the correct option for Cygwin on
the SnapshotAndRel
[ http://issues.apache.org/jira/browse/DERBY-1652?page=all ]
Yip Ng updated DERBY-1652:
--
Fix Version/s: 10.2.0.0
Derby Info: [Patch Available, Existing Application Impact, Release Note
Needed] (was: [Release Note Needed, Existing Application Impact, Pat
[
http://issues.apache.org/jira/browse/DERBY-883?page=comments#action_12427381 ]
Manish Khettry commented on DERBY-883:
--
Dan could you try the last patch file attached with this bug?
> Enhance GROUP BY clause to support expressions instead
[ http://issues.apache.org/jira/browse/DERBY-883?page=all ]
Manish Khettry updated DERBY-883:
-
Attachment: 883.patch6.txt
Minor correction to previous patch.
> Enhance GROUP BY clause to support expressions instead of just column
> references.
> -
[ http://issues.apache.org/jira/browse/DERBY-883?page=all ]
Manish Khettry updated DERBY-883:
-
Attachment: 883.patch6.txt
svn update to revision 430199. Hopefully this patch will apply cleanly.
> Enhance GROUP BY clause to support expressions instead
Suresh Thalamati wrote:
Is it really necessary to use TABS on an existing code files with the
tabs. I am wondering if it would be ok to use 4/8 spaces instead to
match the surrounding code.
Most folks set their editors to have 4 space tabs , so if you use a 4
space tab it looks ok, but if
I'm seeing the following behavior when running the "ant sign" target
from tools/release. I'm running on cygwin. Would appreciate advice.
1) The default md5.options from tools/ant/packaging.tmpl is "-q". On
cygwin this produces md5 output consisting of a hash followed by a
filename. I notice th
Oh, one more thing, the database I have heard us compared with is HSQL.
Folks don't expect us to be equivalent, given that HSQL is in-memory,
but they do complain that the difference is just a little too much, from
basically instantaneous to 10s of seconds...
The use cases I have heard of are
Hi, Mike. Thanks for wanting to participate. My first step I was
planning to do was to do some measurements, as you suggested.
I was going to start with my own machine, which is a laptop running
Solaris x86. But I suspect a lot of folks care about XP and Linux. I
can create a test and we c
Kathey Marsden wrote:
Kathey Marsden wrote:
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 to use TA
I would like to participate in the discussion on this, let me know what
you prefer (list, jira, wiki). As dan said I believe there are many
parts to this issue and would like to see them broken down. I also do
think there is a perception issue also and not quite sure how to
address it, do the db
[ http://issues.apache.org/jira/browse/DERBY-1661?page=all ]
Sunitha Kambhampati resolved DERBY-1661.
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks Mike for the commit.
> Create index on large tables fails with too many o
[ http://issues.apache.org/jira/browse/DERBY-1636?page=all ]
Laura Stewart reassigned DERBY-1636:
Assignee: Laura Stewart
> document encryption of an un-encrypted database and re-encryption with new
> password/key.
> --
[ http://issues.apache.org/jira/browse/DERBY-1551?page=all ]
Laura Stewart reassigned DERBY-1551:
Assignee: Laura Stewart
> Update documentation to indicate procedures can be called from triggers
> (DERBY-551)
> -
[ http://issues.apache.org/jira/browse/DERBY-1660?page=all ]
Sunitha Kambhampati updated DERBY-1660:
---
Attachment: bulkinsert.test.diff.txt
bulkinsert.test.stat.txt
The fix for this issue has already been committed (Thanks Mike). I a
Hi David -
I am planning on documenting this feature in the next few days...
On 8/10/06, David Van Couvering <[EMAIL PROTECTED]> wrote:
DERBY-1551 - Update documentation to indicate procedures can be called
from triggers (DERBY-551). I think this is a key enhancement and should
be more than
I think this is fine. Once this coding convention is finalized, the wiki page http://wiki.apache.org/db-derby/DerbyContributorChecklist should be updated.
YipOn 8/10/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote:
> I think that we should probably have a formal vote nowThis seems fine to me.I sugg
[ http://issues.apache.org/jira/browse/DERBY-1655?page=all ]
Laura Stewart updated DERBY-1655:
-
Attachment: derby1655_ref.diff
derby1655_ref_html.zip
Attached a patch and html.zip file with the updates to the Ref Manual for
the XML suppo
On 8/10/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
I think this would be very useful. Where should we put this information?
The release page seems like an obvious place for it, since it will be
specific to the release.
And another question: At this point, my builds create the following
opti
[ http://issues.apache.org/jira/browse/DERBY-1661?page=all ]
Mike Matrigali updated DERBY-1661:
--
I have reviewed and committed this change. To me I think this is a reasonable
1st step to addressing this
issue, it should avoid most errors when doing large
FYIBegin forwarded message:From: Bill Shannon <[EMAIL PROTECTED]>Date: August 10, 2006 3:49:53 PM PDTTo: [EMAIL PROTECTED]Cc: legal-discuss@apache.org, Craig L Russell <[EMAIL PROTECTED]>Subject: Re: Derby and the JCP We've approved an update to the spec license for non-final specs thatremoves the
[ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]
Kathey Marsden resolved DERBY-1456.
---
Fix Version/s: 10.1.3.2
Resolution: Fixed
Checked into 10.1
Date: Thu Aug 10 14:20:52 2006
New Revision: 430534
URL: http://svn.apache.org/viewvc
[ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]
Kathey Marsden reopened DERBY-1456:
---
> Network Server agentError calls log only to console and are hard to diagnose
> ---
[
http://issues.apache.org/jira/browse/DERBY-1621?page=comments#action_12427363 ]
Yip Ng commented on DERBY-1621:
---
Another problem with SPS recompilation is that it is using 2 different
transactions - one from the user for stored dependencies (SYS
[ http://issues.apache.org/jira/browse/DERBY-1466?page=all ]
Kathey Marsden updated DERBY-1466:
--
Fix Version/s: 10.1.3.2
> Network Server should flush the PrintWriter after console output
> ---
[ http://issues.apache.org/jira/browse/DERBY-1466?page=all ]
Kathey Marsden closed DERBY-1466.
-
t
> Network Server should flush the PrintWriter after console output
>
>
> Key:
[
http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12427361 ]
Deepa Remesh commented on DERBY-1522:
-
I had briefly looked at this task as I was working on DERBY-1521. I think we
can cover the testing suggested by doing th
[ http://issues.apache.org/jira/browse/DERBY-1664?page=all ]
David Van Couvering reassigned DERBY-1664:
--
Assignee: David Van Couvering
> Derby startup time is too slow
> --
>
> Key: DERBY-1664
>
> I think that we should probably have a formal vote now
This seems fine to me.
I suggest reformatting the main paragraph to make it slightly more explicit
that we are adopting these conventions incorporating these amendments. So
I am suggesting something like this:
Derby uses the "Code Convent
Unless someone objects, I hope to create the 10.2 branch and build the
first beta candidate tomorrow. I'm expecting that this candidate will be
called
10.2.1.0 beta
Is that right or should I call this candidate something else?
There are currently 2 Blockers and 4 Urgent issues preventing us
When I run derbyall on my machine, I get a lot diffs with the i18n
tests, of the form
< ERROR XIE0J: Un delimitador no es v EnC:>225< lido o se ha utilizado m
EnC:>225< s de una vez.
55a55
> ERROR XIE0J: Un delimitador no es v?lido o se ha utilizado m?s de una
vez.
Does anyone know what I
[ http://issues.apache.org/jira/browse/DERBY-1663?page=all ]
David Van Couvering closed DERBY-1663.
--
Resolution: Fixed
I upgraded to Ant 1.6.5 and the problem went away. Thanks, Andrew!
> java -jar derbyrun.jar ij gets "Duplicate name in Manifest:
DERBY-1626 - TransactionTable.sql fails - I think we need to keep this
although is that still an issue, as I haven't seen this failure lately
DERBY-1566 - We still need to document the new SQL States, this should
be done before the release.
DERBY-1551 - Update documentation to indicate proced
[ http://issues.apache.org/jira/browse/DERBY-1667?page=all ]
Rajesh Kartha updated DERBY-1667:
-
Summary: Future Backups fails with "ERROR XSRS4: Error renaming file"
after a consistency check is performed on the Backedup database and is not
shutd
A B updated DERBY-688:
--
Attachment: d688_phase4_v2.patch
Thanks for the quick response Army!
I am intending to review and commit the phase4 and phase5 patches tonight.
thanks,
bryan
[
http://issues.apache.org/jira/browse/DERBY-1668?page=comments#action_12427354 ]
Rajesh Kartha commented on DERBY-1668:
--
The first question that comes to my mind is:
Did you start the server on Linux using the -h option allowing clients
Unable to connect using Windows client
--
Key: DERBY-1668
URL: http://issues.apache.org/jira/browse/DERBY-1668
Project: Derby
Issue Type: Bug
Components: Network Client
Affects Versions: 10.1
[
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 and it is not
We talked about using the normal/low urgency unassigned 10.2 issues to
track high value 10.2 bug fix candidates that can be fixed in the
release timeframe.. Probably time to weed down that list. Question:
What date should I now use for this assessment?
There are 63 unassigned 10.2 fix ca
I think this would be very useful. Where should we put this information?
And another question: At this point, my builds create the following
optional artifacts:
1) The JDBC4 support.
2) The osgi support class EmbeddedActivator
3) The jsr169 support
Are there any other optional artifacts which
Future Backups fails with "ERROR XSRS4: Error renaming file" after a
consistency check is performed on the Backedup database
Key: DERBY-1667
In the previous releases has their been documentation about how the jars
were built? I've never seen any, but I've never looked for it. Seems
like it would be useful for resolving any strange bugs later that are
compiler/environment related. Something like:
os platform - linux
java compiler(s) - S
Rick Hillegas wrote:
> I believe I am able to build the small device support now--although I
> must still rely on the community to test this functionality. Here are
> the jsr169-related build artifacts which appear for me now. Am I missing
> something?
Looks good to me. I'm sure the snapshot/alph
[
http://issues.apache.org/jira/browse/DERBY-1130?page=comments#action_12427337 ]
Sunitha Kambhampati commented on DERBY-1130:
Thats makes sense. Thanks Deepa for the explanation.
The patch (d1130-client-v1.patch) looks good to me.
I believe I am able to build the small device support now--although I
must still rely on the community to test this functionality. Here are
the jsr169-related build artifacts which appear for me now. Am I missing
something?
Thanks,
-Rick
trunk/classes/org/apache/derby/impl/jdbc/EmbedCallableS
[
http://issues.apache.org/jira/browse/DERBY-1666?page=comments#action_12427333 ]
Andrew McIntyre commented on DERBY-1666:
These are names of the columns in the result set returned from
DatabaseMetaData.getTables. Having just read throug
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Assignee: David Van Couvering
Derby Info: [Patch Available]
Not really a "patch", since it needs to be converted to DITA, but you get the
i
[
http://issues.apache.org/jira/browse/DERBY-1659?page=comments#action_12427331 ]
David Van Couvering commented on DERBY-1659:
Attached HTML files for each of the SHOW commands (which all appear to be new -
at least, they're not docu
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Attachment: ShowViews.html
> Document describe and show tables functionality
> ---
>
>
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Attachment: Describe.html
> Document describe and show tables functionality
> ---
>
>
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Attachment: ShowSynonyms.html
> Document describe and show tables functionality
> ---
>
>
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Attachment: ShowTable.html
> Document describe and show tables functionality
> ---
>
>
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Attachment: ShowSchemas.html
> Document describe and show tables functionality
> ---
>
>
[ http://issues.apache.org/jira/browse/DERBY-1659?page=all ]
David Van Couvering updated DERBY-1659:
---
Attachment: ShowProcedures.html
> Document describe and show tables functionality
> ---
>
>
[
http://issues.apache.org/jira/browse/DERBY-1130?page=comments#action_12427330 ]
Deepa Remesh commented on DERBY-1130:
-
Thanks Sunitha for looking at the patch.
I moved updateDataSourceValues method call from getConnection to
setConnecti
[
http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427328 ]
Laura Stewart commented on DERBY-1057:
--
Based on the comments from Mamta, I will need to generate new patches for th
Developers Guide and the Reference Manual
Show Views and Show Synonyms has confusing column names in results
--
Key: DERBY-1666
URL: http://issues.apache.org/jira/browse/DERBY-1666
Project: Derby
Issue Type: Bug
Jean T. Anderson (JIRA) wrote:
> [
> http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427325
> ]
>
> Jean T. Anderson commented on DERBY-1057:
> -
>
> Committed patch derby1057_tuning4.diff, which updates the Tuning
[
http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427325 ]
Jean T. Anderson commented on DERBY-1057:
-
Committed patch derby1057_tuning4.diff, which updates the Tuning Guide.
Patches still need to be approved and co
Incorrect JavaDoc for Qualifier interface
-
Key: DERBY-1665
URL: http://issues.apache.org/jira/browse/DERBY-1665
Project: Derby
Issue Type: Bug
Components: Javadoc
Reporter: Andy
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 b
[
http://issues.apache.org/jira/browse/DERBY-1130?page=comments#action_12427318 ]
Sunitha Kambhampati commented on DERBY-1130:
Thanks Deepa for the d1130-client-v1 patch. The patch applies cleanly in my
eclipse ide [with a fuzz fact
[ http://issues.apache.org/jira/browse/DERBY-1664?page=all ]
David Van Couvering updated DERBY-1664:
---
Issue Type: Improvement (was: Bug)
> Derby startup time is too slow
> --
>
> Key: DERBY-1664
>
Deepa Remesh (JIRA) wrote:
> [
> http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427289
> ]
>
> Deepa Remesh commented on DERBY-1057:
> -
>
> Thanks Laura for addressing my comments. I looked at the updated html file
>
[ http://issues.apache.org/jira/browse/DERBY-1641?page=all ]
Mike Matrigali updated DERBY-1641:
--
Component/s: SQL
Adding SQL as component. Without debugging it is only a guess, but in my
experience this kind of problem is
almost always a SQL componen
[
http://issues.apache.org/jira/browse/DERBY-1663?page=comments#action_12427311 ]
Andrew McIntyre commented on DERBY-1663:
This is especially weird because the manifest file that is passed in as the
manifest is correct, but somehow what
this seems like an improvement request, not a bug.
David Van Couvering (JIRA) wrote:
Derby startup time is too slow
--
Key: DERBY-1664
URL: http://issues.apache.org/jira/browse/DERBY-1664
Project: Derby
Issue T
[ http://issues.apache.org/jira/browse/DERBY-1641?page=all ]
Kathey Marsden updated DERBY-1641:
--
Component/s: Store
put this as component store. Not sure if that is right.
> Conglomerate requested does not exist after syscs_import_table with FK
> -
1 - 100 of 198 matches
Mail list logo
