://issues.apache.org/jira/browse/DERBY-4733
Project: Derby
Issue Type: Bug
Components: Store
Affects Versions: 10.6.1.0
Environment: Windows XP
Reporter: David Van Couvering
If you exit a process that is in the middle of booting a database
[
https://issues.apache.org/jira/browse/DERBY-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-4733:
---
Attachment: CorruptMePlease.java
Here is the simple program I used to recreate
[
https://issues.apache.org/jira/browse/DERBY-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-4733:
---
Attachment: corruptme.zip
This is the database that can't be opened.
Get error
[
https://issues.apache.org/jira/browse/DERBY-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885699#action_12885699
]
David Van Couvering commented on DERBY-4733:
Looking at this more closely
/browse/DERBY-4639
Project: Derby
Issue Type: Bug
Affects Versions: 10.5.3.0
Reporter: David Van Couvering
Create a program that issues CREATE TABLE against an existing table every five
seconds, ignoring the exception that the table already exists.
Observe
[
https://issues.apache.org/jira/browse/DERBY-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580904#action_12580904
]
David Van Couvering commented on DERBY-315:
---
Fine with me...
jdbcapi
I think the standard user won't read our release notes, and won't know
that the axe will fall, be it in 10.4 or 10.5. And I think you're
right, the longer we wait, the more users will be impacted.
David
On Jan 14, 2008 10:44 AM, Kathey Marsden [EMAIL PROTECTED] wrote:
Rick Hillegas wrote:
I like this, this seems like a good compromise. If you are using
localhost, then you are using it for personal development, testing and
use. If you listen outside of localhost, then you're up and running
and secure by default seems much more important.
David
On Nov 8, 2007 12:13 PM, Kathey
IMHO, if we are breaking a lot of existing applications, then it was
not a compatible change, and needs to be turned off. I understand the
value of secure by default' but I think this has to be balanced
against the value of Derby as a very quickly easy to use and run
database which makes it a
There's also a very good static analysis tool called FindBugs that
we're using to great effect in NetBeans. See
http://findbugs.sourceforge.net/
On Nov 2, 2007 7:46 AM, John Embretsen [EMAIL PROTECTED] wrote:
Did you know there is a new tool in town that can detect CRAPpy Java code?
Are you
[
https://issues.apache.org/jira/browse/DERBY-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-1567:
---
Assignee: (was: David Van Couvering)
generateClientMessageTest.sh is broken
[
https://issues.apache.org/jira/browse/DERBY-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-1458:
---
Assignee: (was: David Van Couvering)
Add MessageBundleTest to build script
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering reassigned DERBY-2469:
--
Assignee: Francois Orsini (was: David Van Couvering)
I think Francois
Hi, Slamak. I am the database architect for NetBeans, and also a
committer on Derby.
You can actually change the database directory using Tools-Java DB
Database-Database Directory.
However, it is currently hard to set other properties, such as host
and port number. And it doesn't work well
As a user, in particular I would like to see some of those yucky
security exceptions with the network server get resolved (or must
those be done in a feature release?)
David
On 10/3/07, Kathey Marsden [EMAIL PROTECTED] wrote:
Bernt M. Johnsen wrote:
I think a 10.3 update release at the end of
Hillegas [EMAIL PROTECTED] wrote:
Yesterday, a number of derby-dev folks had lunch in San Francisco: David
van Couvering, Lars Heill, Rick Hillegas, Myrna van Lunteren, Kathey
Marsden, Mike Matrigali, and Bryan Pendleton. Here are the highlights of
the Derby-related part of our conversation:
Big news
+1
On 9/26/07, Rick Hillegas [EMAIL PROTECTED] wrote:
+1
Rick Hillegas wrote:
Please vote on whether we should require that developers use a Java 5
(or later) compiler in order to build Derby. This means that the shell
window running the build should have its JAVA_HOME pointed at a Java
No objections.
On 9/25/07, Bernt M. Johnsen [EMAIL PROTECTED] wrote:
Another issue: When I do buildjars I get
java.lang.SecurityException
at
org.netbeans.TopSecurityManager.checkSetSecurityManager(TopSecurityManager.java:351)
at
Hi, all. I was trying to add information about where database
directories are stored for a given Network Server run by adding more
information to sysinfo.
As a first step, in NetworkServerImpl, I added the following:
retval.put(Property.SYSTEM_HOME_PROPERTY,
I think J2ME support is very important.
As another data point, NB requires that you build in JDK 1.5 just for
the reason you state, Mike: to avoid accidental use and checkin of JDK
1.6-specific features. The ant script actually prevents you from
compiling with JDK 1.6 unless you set a specific
Hm, I didn't see the diff, but if it works for you, check it in. It's
not like you'll break the build. I'll check it out and see if it
works for me.
David
On 9/21/07, Bernt M. Johnsen [EMAIL PROTECTED] wrote:
David Van Couvering wrote (2007-09-20 09:07:38):
Has anyone added ant.jar
Has anyone added ant.jar to the project libraries in the project
metadata checked in to Derby? Seems like we should do that.
Thanks,
David
On 9/18/07, Dag H. Wanvik [EMAIL PROTECTED] wrote:
Øystein Grøvlen [EMAIL PROTECTED] writes:
With the help of John's excellent writeup at
It doesn't seem like a lot of work to add this support:
- Add a column to the user metadata (I'm assuming we have such a
thing) indicating default role
- At connection time, set the role to the default role (can be
overriden later by SET ROLE), or null if there is no default role.
I agree,
I would like to add JNLP-based storage engine. I don't know if I have
the cycles to do it, but I'd like to try to work on it. If anyone
wants to join in on the fun, let's talk.
David
On 9/19/07, Bernt M. Johnsen [EMAIL PROTECTED] wrote:
Hi,
I suggest a 10.4 feature release of Derby in Q1
Wow, that's looking ahead. You go, Bernt!
On 9/19/07, Bernt M. Johnsen [EMAIL PROTECTED] wrote:
Hi,
I suggest a 10.4 feature release of Derby in Q1 2008 and I volunteer
as Release Manager for that release.
I have started a wiki page
http://wiki.apache.org/db-derby/DerbyTenFourRelease for
Hi, Bernt. Yes, I encountered this too. I am researching it.
Someone in NB has suggested that our build.xml is assuming that the
ant jar files are always in the classpath, and under NB they are not.
It means adding the ant jar files to the classpath for this target.
I'll investigate this and
Well, this is a standards-based product, but IMHO in this case I think
the standard is being silly. Call me a whiner.
I suspect most tools do *not* have this kind of intelligence. We can
add it to NB, and probably someone will add it to Eclipse. But what
about Squirrel, Toad, etc., etc. By
any work done through my admin UI.
Thanks,
David
On 9/17/07, Dag H. Wanvik [EMAIL PROTECTED] wrote:
Thanks for looking at this, David!
David Van Couvering [EMAIL PROTECTED] writes:
Hi, Dag. Thanks for this spec, this looks like a nice addition to Derby.
I have a couple of comments
Hi, Dag. Thanks for this spec, this looks like a nice addition to Derby.
I have a couple of comments:
- It would be great to have some examples in addition to showing the
changes to the reference manual. Identify some standard use cases
(Create Role, Grant Role, Revoke Role, Access Resource)
+1 !
On 9/10/07, Rick Hillegas [EMAIL PROTECTED] wrote:
Please vote on whether we should make Dyre Tjeldvoll a committer. The
vote will close at 5:00 pm San Francisco time on Monday September 17.
Since 2005 Dyre has submitted many patches and fielded questions on the
mailing lists. His
Hey, Luigi. I posted a new patch to the bug you were working on, JIRA
DERBY-2649. The patch allows you to build correctly in the Derby
codeline. I also attached a jar file containing a NetBeans Java Web
Start project that tries to use the JNLP storage engine, and a
description of the failures I
Both days work for me!
David
On 9/5/07, Rick Hillegas [EMAIL PROTECTED] wrote:
It's been a long time since we had a Derby lunch in San Francisco. As I
recall, Wednesdays work best for the Bay Area community. Anyone
interested in meeting for lunch on Wednesday September 26? Or if that's
a bad
I just added project files for NetBeans 5.5 and NetBeans 6. I put
them under tools/ide/netbeans. This allows you to quickly be able to
use and build Derby in NetBeans. I find this pretty useful, and
thought you might too.
To use, simply bring up NetBeans, choose File-Open Project, and
browse
I like these sanity checks Vemund.
Then of course, there is nirvana: getting rid of using system
properties for configuring Derby. That is *so* nineties :) And of
course it makes it very hard to have two different Derby systems
running in the same VM, even though they're in different
and produce some discussion
on user/developer needs. I welcome suggestions and thoughts!
Ole Gunnar
Siterer David Van Couvering [EMAIL PROTECTED]:
Hi, Ole. Your analysis seems reasonable. The management
requirements
for Derby are pretty minimal and pretty static, and it is always
good
to keep
How about support for storage using JNLP persistence? I'm hoping we
can see that happen by the next release.
On 7/9/07, Bryan Pendleton [EMAIL PROTECTED] wrote:
What else are people planning to do for the next feature release?
I'm interested in working on the so-called OLAP Window Functions
I m doing some quick sanity tests with NetBeans, and it's looking good
so far. The only problem is, NetBeans ships with a ready-made 10.1
database. When I try to use this with the 10.3 beta, it says it's not
supported to upgrade from 10.1 to 10.3 beta.
I understand not supporting upgrade from
Ooh, thanks, that did it! Basic testing with Derby 10.3 looking good
-- no errors when starting the Network Server, with the release
candidate Myrna put out. Able to view metadata and data, so basic
sanity test is looking good.
I will talk to the NB QA folks about running a fuller set of tests
I didn't get any answer from the user community about about project
file portability between versions, Im going to try another channel...
On 6/28/07, Knut Anders Hatlen [EMAIL PROTECTED] wrote:
David Van Couvering [EMAIL PROTECTED] writes:
I don't know about the guaranteed compatibility
So, the message is, guaranteed compatibility from older to newer
version, but no guarantee from newer version to older version. And,
once you open a project with a newer version, it is auto-upgraded to
that new version's format.
David
On 6/28/07, David Van Couvering [EMAIL PROTECTED] wrote:
I
these cases the NB project
is checked into cvs, and I have been quite successful in opening these
projects.
David
On 6/27/07, Knut Anders Hatlen [EMAIL PROTECTED] wrote:
David Van Couvering [EMAIL PROTECTED] writes:
Having worked in NetBeans for a while, I have noticed that many code
bases
Environment: Java Web Start
Reporter: Luigi Lauro
Assignee: David Van Couvering
Priority: Minor
Attachments: svn-diff-20070329, svn-diff-20070606, svn-diff-20070612
I would love to have Derby write/read to the storage area provided by the
JNLP
Having worked in NetBeans for a while, I have noticed that many code
bases are checked in with an associated NetBeans project directory.
This allows NetBeans users to quickly open up the project and start
using it within NetBeans.
I was thinking of doing the same thing for Derby. I am
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---
Attachment: svn-diff-20070626
Here is an updated patch that builds within Derby
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---
Attachment: jnlptest.jar
This is a NetBeans project (using NetBeans 6) that attempts
I think invalid authentication is incorrect, because actually it
should be this user is not authorized to shut down the database.
The authentication went fine, it's just they aren't authorized. There
is security and there is being completely misleading. The poor user
will scratch their heads,
a release
process that is actually easy and fast to do, rather than the
Herculean Challenge it is today.
David
On 6/14/07, Henri van de Scheur - Sun Norway [EMAIL PROTECTED] wrote:
David Van Couvering wrote:
On 6/13/07, Daniel John Debrunner [EMAIL PROTECTED] wrote:
David Van Couvering wrote:
+1
: Improvement
Components: Network Client
Reporter: David Van Couvering
Priority: Minor
Currently, the only way to specify the securityMechanism property on a client
URL is using the integer value for the property, e.g.
jdbc:derby://localhost:1527/mydb;create=true
/jira/browse/DERBY-2834
Project: Derby
Issue Type: Improvement
Components: Documentation
Reporter: David Van Couvering
Priority: Minor
The documentation you need is in two different places:
http://db.apache.org/derby/docs/10.2/adminguide
On 6/13/07, Daniel John Debrunner [EMAIL PROTECTED] wrote:
David Van Couvering wrote:
+1, I agree it's just too tight for 10.3.
I'd like your response to my proposal for the experimental directory;
right now I'm moving forward with it (for checkin to the trunk *after*
we branch for 10.3
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504330
]
David Van Couvering commented on DERBY-2469:
OK, here is my proposal:
- Let's not try to shove
+1, I agree it's just too tight for 10.3.
I'd like your response to my proposal for the experimental directory;
right now I'm moving forward with it (for checkin to the trunk *after*
we branch for 10.3).
The one thing I want to see is making our daily builds available for
download so that
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---
Fix Version/s: (was: 10.3.0.0)
Dropping from 10.3, it's just too tight. I
I've had other deliverables on my plate so I haven't had much time to
spend on this, but I finally did get this to build in our trunk. I'll
post a patch with the changes I made. It's a real bummer that we
don't have real support for JDK 5, given that JDK 6 is not coming to
the Mac any time
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503972
]
David Van Couvering commented on DERBY-2469:
Myrna: I don't understand why this can't go
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503971
]
David Van Couvering commented on DERBY-2469:
Rats, somehow I'm missing these JIRA comments, I'll fix my
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504061
]
David Van Couvering commented on DERBY-2469:
I agree it needs to get tested, and I'm working
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---
Fix Version/s: 10.3.0.0
Tentatively making this fix-in 10.3, understanding
a shortish-term problem that I don't think deserves a large effort.
David
On 6/9/07, Knut Anders Hatlen [EMAIL PROTECTED] wrote:
David Van Couvering [EMAIL PROTECTED] writes:
I'm a little stumped. All of a sudden my build started failing
compile_iapi_error_jsr169:
compile_reference:
Compiling
Thanks for catching this, Myrna, this would have prevented Luigi's
contribution for JNLP storage factory from going in...
On 6/8/07, Myrna van Lunteren [EMAIL PROTECTED] wrote:
Hi,
You have made, or are showing interest in making, contributions to Apache Derby.
I - and I know the Derby
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502951
]
David Van Couvering commented on DERBY-2469:
Hi, Luigi. It looks like you built this with JDK 6
I'm a little stumped. All of a sudden my build started failing
compile_iapi_error_jsr169:
compile_reference:
Compiling 4 source files to /Users/David/code/derby/trunk/classes
/Users/David/code/derby/trunk/java/engine/org/apache/derby/iapi/types/SqlXmlUtil.java:60:
package org.apache.xpath does
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501968
]
David Van Couvering commented on DERBY-2469:
I think this is great you have done all this work, Luigi
HI, all. I'm on a new machine, and am trying to commit to Derby for
the first time (just trying to update BUILDING.txt based on my
experience with a Mac).
I used svn commit --username davidvc --password BUILDING.txt but
I get the following error:
subversion/libsvn_client/commit.c:873:
Thanks for the tip, that was it, trying again with https...
On 6/6/07, Jean T. Anderson [EMAIL PROTECTED] wrote:
Did you check out with https or http in the URL? --Be sure to use https.
-jean
David Van Couvering wrote:
HI, all. I'm on a new machine, and am trying to commit to Derby
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502142
]
David Van Couvering commented on DERBY-2469:
Hi, Luigi, I don't know how you generated this patch
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502144
]
David Van Couvering commented on DERBY-2469:
Luigi, correct me if I'm wrong, but JNLP provides a way
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---
Comment: was deleted
Java Web Start JNLP PersistenceService API storage support
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502152
]
David Van Couvering commented on DERBY-2469:
Hi, Luigi. I was able to apply the patch. A couple
[
https://issues.apache.org/jira/browse/DERBY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Van Couvering updated DERBY-2469:
---
Fix Version/s: 10.3.0.0
Assignee: David Van Couvering
I made this change
?
Thanks,
-Rick
David Van Couvering wrote:
I agree, changing the default policy file as Dan suggests does not
seem to be backward compatible.
I believe it would be worthwhile to publicize the decision to go with
(3) and the reasons why to the derby-user list. At least way we have
given our users
:
David Van Couvering wrote:
I am also torn between 2 and 3 but am leaning towards 2, especially if
we document this is what we should do.
Does Derby 10.3 have a beta period? If we can get a strong amount of
users testing Derby 10.3 in beta we might get some good feedback if we
go with option 2
I am also torn between 2 and 3 but am leaning towards 2, especially if
we document this is what we should do.
Does Derby 10.3 have a beta period? If we can get a strong amount of
users testing Derby 10.3 in beta we might get some good feedback if we
go with option 2. If we start with 3 from
When we discussed this previously, I had asked Rick to take this to
the users, and he did, see:
http://www.nabble.com/Naming-the-next-Derby-feature-release-tf3329320.html#a9257363
I thought that for most folks, authentication is turned OFF. I also
thought that the default for Derby is to have
+1 to option 3. What's crucial to me is that someone who is running
in a very secure environment or who doesn't care about the security of
the database (e.g. during development) does not have to deal with this
usability overhead. Good to have for production, but keep it out of
the way for
I just did a perusal of the incompatibilities of 10.3. My apologies
for not looking sooner. I would venture to guess that other users
have been equally lazy - I think we generally expect the Derby team to
do the right thing and not introduce incompatibilities between
releases. I really really
process, it shouldn't impact any NB code trying to do file
I/O and such.
Then we wouldn't get bitten by this when a user upgrades to 10.3.
David
On 5/30/07, Daniel John Debrunner [EMAIL PROTECTED] wrote:
David Van Couvering wrote:
Also, if I understand things correctly, then when you upgrade
On 5/30/07, Rick Hillegas [EMAIL PROTECTED] wrote:
I don't know how to measure the residual exposure here. I have not had
much success trawling derby-user for advice.
You might try nbusers (and the matching list on Eclipse). There seem
to be more database users there than on derby-user :)
Something that may be of interest to Derby as well...
-- Forwarded message --
From: Craig L Russell [EMAIL PROTECTED]
Date: May 16, 2007 9:21 PM
Subject: Fwd: Lock-free HashMap
To: [EMAIL PROTECTED]
Don't know if anyone caught Cliff's preso at Java One...
Anyone want to take a
Wow, great news. Molasses does move, albeit slowly...
Rick Hillegas wrote:
Yesterday, the Open Group Board of Directors approved Version 4 of the
DRDA spec. This is the new version which includes support for the XML
and Boolean datatypes. You can get the spec from the Open Group site:
:
On 4/20/07, David Van Couvering [EMAIL PROTECTED] wrote:
I'm for 10.3, 11 seems a little severe.
I would also like to see us nail down the interface stability work I
started and get a vote on that. I was thinking two votes:
- One on our policies about interface stabilities - what the various
I'm for 10.3, 11 seems a little severe.
I would also like to see us nail down the interface stability work I
started and get a vote on that. I was thinking two votes:
- One on our policies about interface stabilities - what the various
stability classifications mean in terms of our
Thanks for taking this on, Myrna! A really great service for the community.
David
Myrna van Lunteren wrote:
Hi,
I haven't noticed anyone offering to be release manager for 10.3...so
I'm offering to be the release manager.
Thx to Rick and Kathey for keeping the 10.3 coals
I thought that you could also do this by modifying
org/apache/derby/module.properties (as available in your classpath).
I'm not sure what entry to modify, but this is what is used to identify
what implementation use for various interfaces (such as StorageFactory).
David
Francois Orsini
Hm, I guess this would work. It would be nice if some day we supported
storing all tables in a single file...
David
Bryan Pendleton wrote:
Is there a way to reduce this number, by storing several/all tables
into one 'data' file?
You could accomplish this in your application, by defining a
Hi, Luigi. Another pot-shot from the side :)
I think it's great you are already submitting some code! Very impressed!
I'd review this, except it's really not my area of expertise. Heck,
I'll look at it anyway.
But I wanted to alert you to how Apache communities work. You may
proudly
Hi, Luigi. Thanks for submitting this!
Here are my comments:
- Your code is very well written - clear, well-commented, nicely
structured!
- Sigh. Does the JNLP persistence service have no concept of a
directory? I hate the length == 0 approach of identifying a
directory. But sometimes
OK, thanks.
Luigi Lauro wrote:
On 27 Mar 2007, at 20:01, David Van Couvering wrote:
- Don't you need to close any open files on shutdown? This highlights
my ignorance of this area of the code...
I noticed now the 'on shutdown'.
Regarding persistent entities, no, I don't need to close
Do you have a workaround for this bug?
David
Luigi Lauro wrote:
Something I forgot.
On 27 Mar 2007, at 20:01, David Van Couvering wrote:
Perhaps we can provide some feedback to the JNLP folks?
Regarding this, no I don't think we can legitly ask for a more capable
PersistenceService
, then
these new tests/configurations should be added to derbyall. I don't
think this is required for initial checkin, though.
Make sense?
Thanks,
David
Luigi Lauro wrote:
On 27 Mar 2007, at 20:01, David Van Couvering wrote:
Hi, Luigi. Thanks for submitting this!
Thanks for replying.
Here
Hi, Luigi. You might take your JNLP questions to the open source JDK
communities:
OpenJDK: https://openjdk.dev.java.net/
Apache Harmony: http://harmony.apache.org/
If that doesn't work out, let me know, and I'll try and find some
contacts here at Sun.
Great to see progress on this! As
Great! Let us know how we can help. As you go through this, you'll
probably get gentle corrections about approach, process, style, etc.
Hopefully this won't be too off-putting.
For example, a general rule is to not cross-post to two Apache aliases.
This sounds like a development discussion
+1
David
Rick Hillegas wrote:
Please vote on whether we should make Dag Wanvik a Derby committer. The
vote will close at 5:00 pm San Francisco time on Monday March 19.
Last year, Dag lead a team of developers in implementing Scrollable
Updatable ResultSets. Recently he investigated how to
in a public place but a quick
look at the derby wiki was negative.
*/David Van Couvering [EMAIL PROTECTED]/* wrote:
This is happening, and timing is tight. Ross Gardler
([EMAIL PROTECTED]) would like to know if you're interested in
being a
mentor. This is not a commitment to actually
This is happening, and timing is tight. Ross Gardler
([EMAIL PROTECTED]) would like to know if you're interested in being a
mentor. This is not a commitment to actually mentor, nor is it a
guarantee that you'll have a mentee.
Ross says:
So, please express your interest in being a mentor by
until now, the consensus on derby-dev?
Regards,
-Rick
David Van Couvering wrote:
I wanted the question to be more of the form is compatibility between
minor releases more important to you than client/server
secure-by-default functionality? -- with the suspicion that an
embedded user doesn't really
Yes, this is done all the time. If you want to manage it more
carefully, you can alway create sub-tasks for the umbrella issue. But I
don't know if that's really necessary for doc patches...
David
Laura Stewart wrote:
Kim Haase has contributed some really great patches to DERBY-1920 for
I wanted the question to be more of the form is compatibility between
minor releases more important to you than client/server
secure-by-default functionality? -- with the suspicion that an embedded
user doesn't really care about client/server security and thus would opt
for compatibility. But
requirement and its importance relative to
other requirements should be added to the charter.
3) As far as I can tell (from the Derby website), the idea that an
incompatibility is OK iff you bump the major version number has not
been formally accepted/ratified by the Derby community. David van
I would like to suggest we include the user community on this
discussion. It is the users who are most impacted by decisions around
security and compatibility.
Making the call that secure-by-default trumps frictionless upgrade
really needs to be done with their input and overall approval.
1 - 100 of 1161 matches
Mail list logo
