[
https://issues.apache.org/jira/browse/DERBY-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475608
]
Yip Ng commented on DERBY-264:
--
Hi Laura:
I think in the numeric example of the ORDER BY clause ref page, the following
On 2/23/07, Andrew McIntyre <[EMAIL PROTECTED]> wrote:
Note that I left out the jdbc4 test suite from the target, as I didn't
have jdk16 on my machine at the moment. If someone else would like to
create an alternate target that docs everything if jdk16 is available,
they should feel free to do s
On 2/23/07, Dag H. Wanvik <[EMAIL PROTECTED]> wrote:
Is there a reason why the testing javadocs are not generated by the
javadoc target? I noticed they were not.. and I needed to consult them
on getting up top speed on the JUnit framework.
Inertia? Procrastination? Because this is only the sec
[
https://issues.apache.org/jira/browse/DERBY-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475602
]
Tomohito Nakayama commented on DERBY-908:
-
I think next example in minutes page is for duration which is not s
[
https://issues.apache.org/jira/browse/DERBY-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Tarter updated DERBY-2376:
Attachment: DerbyUtils.diff
> Patch available to make .classpath entries portable - relative to ECL
[
https://issues.apache.org/jira/browse/DERBY-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Tarter updated DERBY-2376:
Summary: Patch available to make .classpath entries portable - relative to
ECLIPSE_HOME (was: Patc
Understand that there was a broken link on the ApacheCon US 2006 site to
my session presentation. I have forwarded that presentation ("The End
of Ossification: The Strategic Opportunities in Open Source") to Rick H
and then on to Jean A for posting. I'll be giving an updated version of
this se
--
Regards,
Aaron J Tarter
When clicking "Add Derby Nature" in the Derby UI Plugin, four entries are
added to the .classpath of the project. These are lib type entries and the
path references are absolute e.g.:
This is problematic since absolute paths do not allow for sharing via an SCM
repository like SVN or CVS. A
[
https://issues.apache.org/jira/browse/DERBY-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Tarter updated DERBY-2376:
Description:
This patch modifies the DerbyUtils class to add variable entries relative to
ECLIPSE_
[
https://issues.apache.org/jira/browse/DERBY-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475590
]
Aaron Tarter commented on DERBY-2376:
-
The current behavior of adding four derby lib entries with absolute path
Patch avaialble to make .classpath entries portable - relative to ECLIPSE_HOME
--
Key: DERBY-2376
URL: https://issues.apache.org/jira/browse/DERBY-2376
Project: Derby
Andrew McIntyre <[EMAIL PROTECTED]> writes:
> On 2/2/07, scott hutinger <[EMAIL PROTECTED]> wrote:
>>
>> I think the important thing, is to move over to fop.93 if possible.
>
> I've just attached a patch to DERBY-2373 that allows an upgrade to FOP
> 0.93. I would appreciate it if any doc builders
"Rajesh Kartha (JIRA)" <[EMAIL PROTECTED]> writes:
This errors probably stem from the changes made for
DERBY-2264-{1,2}. I did no testing on the IBM weme 6.1 platform. Let
me know if you have any issues updating the canons.
I did update the j9_foundation canons, though (no testing).
Dag
> jdbca
[
https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Thalamati updated DERBY-378:
---
Attachment: derby378_1.stat
derby378_1.diff
DERBY -378 (partial)
This patch ad
jdbcapi/users2.sql and jdbcapi/secureUsers.sql fails on IBM weme 6.1
Key: DERBY-2375
URL: https://issues.apache.org/jira/browse/DERBY-2375
Project: Derby
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DERBY-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475560
]
Rajesh Kartha commented on DERBY-2366:
--
With 10.3.0.0 alpha - (510766), I observed the SecureServerTest test st
UNION PROBLEM WITH PARENTHESIS
--
Key: DERBY-2374
URL: https://issues.apache.org/jira/browse/DERBY-2374
Project: Derby
Issue Type: Bug
Affects Versions: 10.2.2.0
Reporter: Kenneth Gee
P
+1
-jean
Jean T. Anderson wrote:
> As required by the ASF ip-clearance process in the Incubator [1],
> please vote to accept the NetworkServer system tests contributed by IBM
> that are attached to the following Jira issue:
>
>https://issues.apache.org/jira/browse/DERBY-2248
>
> I'll close
On 2/2/07, scott hutinger <[EMAIL PROTECTED]> wrote:
I think the important thing, is to move over to fop.93 if possible.
I've just attached a patch to DERBY-2373 that allows an upgrade to FOP
0.93. I would appreciate it if any doc builders out there would some
spare time could try it out and m
[
https://issues.apache.org/jira/browse/DERBY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475534
]
Daniel John Debrunner commented on DERBY-2367:
--
I think if you used the sub-sub protocl 'directory' in y
On 2/23/07, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
1) Step 7 ("Add a new Ant Builder") has a partial last sentence:
"If you get an error that com.sun.tools.javac could not be found and to
check if your JAVA_HOME is set, you may need to go to the Classpath tab
and add tools.jar from your JD
[
https://issues.apache.org/jira/browse/DERBY-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475531
]
Aaron Tarter commented on DERBY-1488:
-
I agree. A feature would help with the current install by grouping the th
[
https://issues.apache.org/jira/browse/DERBY-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre updated DERBY-2373:
---
Attachment: derby-2373.stat
Attaching a stat file which shows all the various jars that are a
[
https://issues.apache.org/jira/browse/DERBY-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre updated DERBY-2373:
---
Attachment: derby-2373.diff
Attaching a patch for this issue. To try it out requires also dow
Upgrade documentation PDF builds to use FOP .93
---
Key: DERBY-2373
URL: https://issues.apache.org/jira/browse/DERBY-2373
Project: Derby
Issue Type: Improvement
Components: Build tools, D
Mamta,
Thanks for taking the time to respond.
I had the developer run this using the embedded driver and attached the
log. It looks like the prepare is failing on the DECLARE.
I have attached the log for your reference.
Regards
Lance
Mamta Satoor wrote:
Lance, I am sure you have already
Andrew McIntyre wrote:
...
> I just put an updated set of instructions on the BuildingDerby page:
>
> http://wiki.apache.org/db-derby/BuildingDerby
>
> that reflects what I do to set up Eclipse from scratch. I left the old
> ones on there for now. I would appreciate if someone could test drive
>
[
https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Tarter updated DERBY-1931:
Attachment: DerbyUtils.diff
This patch modifies the DerbyUtils class to add variable entries relati
[
https://issues.apache.org/jira/browse/DERBY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475498
]
Rick Hillegas commented on DERBY-2196:
--
What should be do about the network startup scripts? Now if you run
sta
[
https://issues.apache.org/jira/browse/DERBY-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475491
]
Aaron Tarter commented on DERBY-1931:
-
I agree that the current behavior of adding four derby lib entries with
a
[
https://issues.apache.org/jira/browse/DERBY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-1920:
-
Attachment: DERBY-1920-adminguide.zip
DERBY-1920-adminguide.diff
Here is another relative
Bryan Pendleton <[EMAIL PROTECTED]> writes:
>> in the datatype code for a binary object, the value may change from
>> a 30Mb array to a 2 byte array, so nulling out the reference before
>> creating a new one is good.
>
> Is there any value to explicitly calling System.gc() in a situation
> such a
Lance, I am sure you have already checked following but wanted to throw them
out anyways
1)Is the temporary table getting referenced by the same connection that
created it?
2)Does your particular scenario work under embedded Derby?
Also, once the connection that created the global table closes, t
[
https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475414
]
A B commented on DERBY-47:
--
Thank you very much for your excellent questions, Mike. My attempted answers
are below...
> Can
[
https://issues.apache.org/jira/browse/DERBY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-2361:
-
Attachment: rrefattribsecmech.dita
DERBY-2361.zip
DERBY-2361.diff
Thanks,
in the datatype code for a binary object, the value may change from a
30Mb array to a 2 byte array, so nulling out the reference before
creating a new one is good.
Is there any value to explicitly calling System.gc() in a situation
such as this?
thanks,
bryan
[
https://issues.apache.org/jira/browse/DERBY-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg closed DERBY-2368.
--
> Modify compatibility/testScript.xml to not run embedded/jvm1.3 case any more
> - not valid after r509863
Knut Anders Hatlen wrote:
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
Knut Anders Hatlen wrote:
[EMAIL PROTECTED] writes:
if ((pageData == null) || (pageData.length !=
pageSize)) {
+// Give a chance for gc to release the old buffer
+page
[
https://issues.apache.org/jira/browse/DERBY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475382
]
Bryan Pendleton commented on DERBY-2367:
Thanks for tracking this code down, Raymond, and I'm glad to hear th
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
> Knut Anders Hatlen wrote:
>> [EMAIL PROTECTED] writes:
>>
>>> if ((pageData == null) || (pageData.length !=
>>> pageSize)) {
>>> +// Give a chance for gc to release the old buffer
>>> +pageData = null;
Document the secure-by-default network server
-
Key: DERBY-2372
URL: https://issues.apache.org/jira/browse/DERBY-2372
Project: Derby
Issue Type: New Feature
Components: Documentation
[Auto-generated mail]
*Daily* 510588/2007-02-22 18:00:42 CET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0430430 090.49% derbyall
068176817 0 352.88% suitesAll
sles
0
Setting a default value for a VARCHAR column fails when column contains data
Key: DERBY-2371
URL: https://issues.apache.org/jira/browse/DERBY-2371
Project: Derby
Is
[
https://issues.apache.org/jira/browse/DERBY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-2220:
-
Derby Info: (was: [Patch Available])
Patch (as comments show) does not implemen
Knut Anders Hatlen wrote:
[EMAIL PROTECTED] writes:
if ((pageData == null) || (pageData.length != pageSize))
{
+// Give a chance for gc to release the old buffer
+pageData = null;
pageData = new byte[pageSize];
Out of curiosity (I have seen similar co
Does anyone have an idea as to why the gobal table cannot be found.
Here is the trace output.
Regards
lance
[TopLink Fine]:
ClientSession(12549034)--Connection(16309502)--Thread(Thread[AWT-EventQueue-0,6,main])--DECLARE
GLOBAL TEMPORARY TABLE session.TL_CMP3_EMPLOYEE (EMP_ID INTEGER NOT
NULL
Issue Subscription
Filter: Derby: JIRA issues with patch available (18 issues)
Subscriber: derby-dev
Key Summary
DERBY-2369 NetworkServerControl.shutdown() takes at least 1.5 seconds, could
be faster.
https://issues.apache.org/jira/browse/DERBY-2369
DERBY-2257 Implementing
[
https://issues.apache.org/jira/browse/DERBY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2196:
-
Attachment: secureServer.html
Attaching rev 8 of the functional spec. This improves the Upgrade s
[
https://issues.apache.org/jira/browse/DERBY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475358
]
Raymond H commented on DERBY-2367:
--
shall I resolve the issue ?
> Derby fails to connect to a formerly properly cre
[
https://issues.apache.org/jira/browse/DERBY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475357
]
Raymond H commented on DERBY-2367:
--
Thanks guys, for giving me the jumstart:
changing:
public String getC
[EMAIL PROTECTED] writes:
> if ((pageData == null) || (pageData.length != pageSize))
> {
> +// Give a chance for gc to release the old buffer
> +pageData = null;
> pageData = new byte[pageSize];
Out of curiosity (I have seen s
[
https://issues.apache.org/jira/browse/DERBY-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475350
]
Daniel John Debrunner commented on DERBY-2369:
--
Thanks for the comment Knut Anders. yes i was running on
[
https://issues.apache.org/jira/browse/DERBY-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen updated DERBY-208:
--
Attachment: LOBLocatorv2.pdf
Uploaded updated version of use cases for locator-based implementat
[
https://issues.apache.org/jira/browse/DERBY-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475342
]
Øystein Grøvlen commented on DERBY-2257:
Question on the ...GETPOSITIONFROM... procedures: Should not the pos
[
https://issues.apache.org/jira/browse/DERBY-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2276:
-
Attachment: RHansenApacheConFinal#WE30pdf.pdf
Attaching Rebecca's talk on 'The End of Ossificatio
Mike Matrigali <[EMAIL PROTECTED]> writes:
> Was there a reason to ship "logical" log records - did that just fit
> with some code you had for other dbs?
>
> I believe Derby trunk is a long way there for someone to implement a
> hot standby using the existing "physical" log records. With the mos
[
https://issues.apache.org/jira/browse/DERBY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475328
]
Raymond H commented on DERBY-2367:
--
Very good thoughts, thanks both of you.
Here goes, and yes, it probably is some
[
https://issues.apache.org/jira/browse/DERBY-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernt M. Johnsen updated DERBY-2356:
Attachment: SSLFuncSpect.txt
derby-2356-v2.stat
derby-2356-v
Yip Ng <[EMAIL PROTECTED]> writes:
>> On 2/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>>
>>It looks like this could be related to the use of an AnyResultSet for
>>the predicate. When EXISTS is applied to a SELECT it seems like the
>>query is re-written as a join... (lots of guessing an
[
https://issues.apache.org/jira/browse/DERBY-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-2370:
--
Attachment: repro.sql
ij script to reproduce the bug.
> EXISTS may return the wrong value for
EXISTS may return the wrong value for sub-queries involving set operations
--
Key: DERBY-2370
URL: https://issues.apache.org/jira/browse/DERBY-2370
Project: Derby
Issue
[
https://issues.apache.org/jira/browse/DERBY-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475294
]
Kristian Waagan commented on DERBY-2367:
It could also be helpful if you had the possibility to download and
[
https://issues.apache.org/jira/browse/DERBY-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475290
]
Knut Anders Hatlen commented on DERBY-2369:
---
The patch looks good. +1 to commit if the tests pass. One mino
On 2/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
It looks like this could be related to the use of an AnyResultSet for
the predicate. When EXISTS is applied to a SELECT it seems like the
query is re-written as a join... (lots of guessing and hand-waving
here...).
I believe its probabl
65 matches
Mail list logo
