[
http://issues.apache.org/jira/browse/DERBY-782?page=comments#action_12361165 ]
Tomohito Nakayama commented on DERBY-782:
-
Current implementation of org.apache.derby.impl.jdbc.EmbedBlob#length() have
some problematic behavior.
If length() method w
[ http://issues.apache.org/jira/browse/DERBY-782?page=all ]
Tomohito Nakayama updated DERBY-782:
Comment: was deleted
> Improvement on org.apache.derby.impl.jdbc.EmbedBlob#length()
>
>
>
[ http://issues.apache.org/jira/browse/DERBY-782?page=all ]
Tomohito Nakayama updated DERBY-782:
Attachment: testLob4.java
Current implementation of org.apache.derby.impl.jdbc.EmbedBlob#length() have
some problematic behavior.
If length() method was
Improvement on org.apache.derby.impl.jdbc.EmbedBlob#length()
Key: DERBY-782
URL: http://issues.apache.org/jira/browse/DERBY-782
Project: Derby
Type: Bug
Components: JDBC
Reporter: Tomohito Nakayama
[ http://issues.apache.org/jira/browse/DERBY-781?page=all ]
Satheesh Bandaram updated DERBY-781:
Description:
Derby's handling of union subqueries in from list can be improved by
materializing invariant resultsets once, rather than creating them man
Materialize union subqueries in select list where possible to avoid creating
invariant resultsets many times.
-
Key: DERBY-781
URL: http://issues.apache.org/jira/browse/DE
I do want to emphasize one point -- I think we're doing OK getting
newbies to work on the "edges" of the code. What I am concerned about
and want to encourage is for people who aren't experts to find ways to
start working on the "core" technology.
Doing design documentation is a good idea, bu
I have attached a patch for this last week and was wondering if
someone can take a look.
Thanks,
Deepa
Considering what Derby does here, does anyone have any comments on the current behavior? IMO, mixing of dml and ddl probably will not be seen in real life application so much. The -ve thing is that the value is not getting generated in its own transaction because of locking issues and is getting ge
We should put nabble on the web page. I think most of us prefer this
over mod_mbox.
David
Jean T. Anderson wrote:
Rick Hillegas wrote:
Thanks, Deepa. Using nabble, I can get my hands on a web page which
displays a thread-initiating message and all of its replies. That's
useful. But I can't
My apologies for not being in on this conversation, I had a bit of a
family emergency and had to be offline for the last five days. Is this
patch getting committed? Is there something I can do to help?
Thanks,
David
Rick Hillegas wrote:
Thanks, Satheesh.
-Rick
Satheesh Bandaram wrote:
Hi Francois,
Francois Orsini wrote:
Hi Satheesh,
Regarding the issues you mentioned:
> 1) Should Derby support upgrading a 10.1 database to 10.2
directly into 'sqlStandard' mode (optionally) or not?
I would say no - as this is a new feature of 10.2, we should let the
user configure
[
http://issues.apache.org/jira/browse/DERBY-766?page=comments#action_12361153 ]
Daniel John Debrunner commented on DERBY-766:
-
I was looking at how language ResultSets are created at runtime. A UNION node
will generate byte code to call this me
[ http://issues.apache.org/jira/browse/DERBY-398?page=all ]
Deepa Remesh updated DERBY-398:
---
Attachment: jdk14_tests.diff
jdk14_tests.status
Attaching a patch 'jdk14_tests.diff' which adds jdk14 suite and some more tests
to run with J2ME/C
[ http://issues.apache.org/jira/browse/DERBY-747?page=all ]
Jean T. Anderson updated DERBY-747:
---
Attachment: masthead_derby5.png
masthead_derby5.png squeezes the white space in the masthead down by 4 pixels
top and bottom and also includes more contex
[ http://issues.apache.org/jira/browse/DERBY-747?page=all ]
Jean T. Anderson updated DERBY-747:
---
Attachment: masthead_derby4.png
masthead_derby4.png shrinks the db project logo by 25% and adds 20 pixels top
and bottom.
> Derby Logo Work
> ---
[ http://issues.apache.org/jira/browse/DERBY-747?page=all ]
Jean T. Anderson updated DERBY-747:
---
Attachment: masthead_derby3.png
masthead_derby3.png is a screenshot that incorporates the derby logo from
masthead_derby2.png on a site built by forrest.
Let us look at the issues and some assumptions. A solution may follow
from it and this definitely needs some debate. The assumptions here are
my proposals only.
My current proposal (attached to Jira) would allow migrating
databases from legacy security mode into sqlStandard mode, but not the
Very cool indeed! :-)
I think this is correct for Brazilian Portuguese; pt_BR
But I am not 100% certain.
One question is the directory layout. Should it be something like
src/en
src/pt_BR
etc?
Should the output be something like
getstarted_en.pdf
getstarted_pt_BR.pdf
I did the following, alt
[ http://issues.apache.org/jira/browse/DERBY-747?page=all ]
Roger Dudler updated DERBY-747:
---
Attachment: masthead_derby2.png
> Derby Logo Work
> ---
>
> Key: DERBY-747
> URL: http://issues.apache.org/jira/browse/DERBY-747
>
[ http://issues.apache.org/jira/browse/DERBY-747?page=all ]
Roger Dudler updated DERBY-747:
---
Attachment: masthead_derby.png
> Derby Logo Work
> ---
>
> Key: DERBY-747
> URL: http://issues.apache.org/jira/browse/DERBY-747
>
[
http://issues.apache.org/jira/browse/DERBY-780?page=comments#action_12361132 ]
Jeff Levitt commented on DERBY-780:
---
While I cant comment on the content (since I can't read Brazilian Portoguese),
I can say that I checked the build of these dita files by
Please read "So this behavior with system locks, one can try to run following sql in ij" as "To see this behavior with system locks, one can try to run following sql in ij"
Also, please read "
-- the insert above fails as expected because there is already a *1* in the table. But the generated val
I looked at Derby code and in fact, Derby does implement the SQL standard by doing the job of getting the generated value and updating the system table SYSCOLUMNS for the next generated value in a transaction of its own. But this does not happen in its own transaction when there are lock issues on
Hi Dan,
> "Daniel" == Daniel John Debrunner (JIRA) wrote:
Daniel> Each column in the insert row that does not allow null as a value and
does not
Daniel> have a default value must be given a value using the appropriate update
method.
Daniel>
Daniel>
Daniel> nullablehas default
Daniel
[ http://issues.apache.org/jira/browse/DERBY-413?page=all ]
Andrew McIntyre resolved DERBY-413:
---
Fix Version: 10.2.0.0
Resolution: Fixed
Committed to trunk with revision 358591.
> Need an easy way to change the localhost string in the Netwro
[ http://issues.apache.org/jira/browse/DERBY-212?page=all ]
Knut Anders Hatlen updated DERBY-212:
-
Attachment: DERBY-212-parsePKGNAMCSN.diff
throughput.png
throughput-normalized.png
I have uploaded a patch (DERBY-212-p
[
http://issues.apache.org/jira/browse/DERBY-100?page=comments#action_12361121 ]
Daniel John Debrunner commented on DERBY-100:
-
OK - the coffee has kicked in and I understand the allow null comment in the
spec. I'd forgotten that nullable meant
[
http://issues.apache.org/jira/browse/DERBY-100?page=comments#action_12361118 ]
Daniel John Debrunner commented on DERBY-100:
-
In Positive test 47 you check to see what happens if you call insertRow()
without setting any of the column values.
Y
Hi Jean,
I find that I have to wire in the following:
o All of the jar files in trunk/tools/java
o The compiled Derby class tree
o The DB2JCC jar and license file
I'm attaching a script which I use to setup the classpath.
Regards,
-Rick
Jean Morissette wrote:
Hi devs,
I try to figure how
[
http://issues.apache.org/jira/browse/DERBY-100?page=comments#action_12361115 ]
Daniel John Debrunner commented on DERBY-100:
-
Looks good generally, some minor comments:
In EmbedResultSet.moveToInsertRow you always generate a new blank row, su
Right - at least you get a choice...On 12/22/05, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
Francois Orsini wrote:>>3) Dan raised an important question about whether
> defaultConnectionMode should be made a database-only property> > and without affecting existing applications. I am curr
Francois Orsini wrote:
>>3) Dan raised an important question about whether
> defaultConnectionMode should be made a database-only property
> > and without affecting existing applications. I am currently thinking
> if defaultConnectionMode is set to sqlStandard \
> > as a database property
Halley Pacheco de Oliveira wrote:
> Andrew,
>
> I did what you told me to do and the contributed translation is in
>
> Derby
> Getting Started manual translated into Brazilian Portuguese
Seems like this is potentially a bug enough contribution to require
Halley to have an ICLA on file.
Halley,
I finally got back to this issue hat have been laying around for way
too long. I have attached a new patch to JIRA that should address
Suresh's review comments. Could someone please review it?
--
Øystein
> "ØG" == Øystein Grøvlen (JIRA) writes:
ØG> [
http://issues.apache.org/ji
[ http://issues.apache.org/jira/browse/DERBY-774?page=all ]
Bernt M. Johnsen resolved DERBY-774:
Fix Version: 10.2.0.0
Resolution: Fixed
> DRDAConnThread::doneData should use statically allocated SQLException objects
> -
Andrew,
I did what you told me to do and the contributed translation is in
Derby
Getting Started manual translated into Brazilian Portuguese
Created: Today 12:05 PM Updated: Today 12:10 PM
Component/s:Documentation
Affects Version/s: 10.1.1.0
Fix Version/s: None
KEY DERBY-780
[
http://issues.apache.org/jira/browse/DERBY-298?page=comments#action_12361100 ]
Øystein Grøvlen commented on DERBY-298:
---
The recently attached patch (derby-298a.diff) addresses Suresh's
review comments. The only major change from the previous patch i
[ http://issues.apache.org/jira/browse/DERBY-780?page=all ]
Halley Pacheco de Oliveira updated DERBY-780:
-
Attachment: getstart.tgz
Getting Started manual translated into Brazilian Portuguese DITA files tar
zipped.
> Getting Started manual
Getting Started manual translated into Brazilian Portuguese
---
Key: DERBY-780
URL: http://issues.apache.org/jira/browse/DERBY-780
Project: Derby
Type: Improvement
Components: Documentation
Versions: 10.
[ http://issues.apache.org/jira/browse/DERBY-298?page=all ]
Øystein Grøvlen updated DERBY-298:
--
Comment: was deleted
> rollforward will not work correctly if the system happens to crash
> immediately after rollforward backup.
> ---
[ http://issues.apache.org/jira/browse/DERBY-298?page=all ]
Øystein Grøvlen updated DERBY-298:
--
Attachment: derby-298a.diff
This new patch should address the issues from the last review. The only file
that has changed from the earlier patch is
java/e
Hi Satheesh,
Regarding the issues you mentioned:
> 1) Should Derby support upgrading a 10.1 database to 10.2 directly into 'sqlStandard' mode (optionally) or not?
I would say no - as this is a new feature of 10.2, we should let the
user configure it on its own after upgrade. Also what does it
Well I see these as constants being defined as part of some
interface(s) (space), hence they should be de-referenced through the
interface as it is done within:
org.apache.derby.jdbc.EmbedXAConnection
[...]
if (ret == XATransactionController.XA_OK) {
tranState.
44 matches
Mail list logo
