[
https://issues.apache.org/jira/browse/DERBY-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541012
]
Bernt M. Johnsen commented on DERBY-3186:
-
Thanks Dan. If an external authentication provider is defined
[
https://issues.apache.org/jira/browse/DERBY-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541008
]
Bernt M. Johnsen commented on DERBY-3185:
-
The following statement in
[
https://issues.apache.org/jira/browse/DERBY-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541002
]
Knut Anders Hatlen commented on DERBY-3185:
---
The first paragraph about SET ISOLATION statement in the
[
https://issues.apache.org/jira/browse/DERBY-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg updated DERBY-3188:
---
Environment:
OS: All(?)
JVM: Sun Microsystems Inc. 1.5.0, Sun Microsystems Inc. 1.4.2
was:
OS:
[
https://issues.apache.org/jira/browse/DERBY-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541013
]
Knut Anders Hatlen commented on DERBY-3185:
---
Bernt wrote:
the fact that REPEATABLE READ in SQL is NOT the
Replication: Add connection url command options for starting and stopping master
Key: DERBY-3189
URL: https://issues.apache.org/jira/browse/DERBY-3189
Project: Derby
[
https://issues.apache.org/jira/browse/DERBY-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3189:
-
Component/s: JDBC
Description:
Add commands to start and stop the replication
[
https://issues.apache.org/jira/browse/DERBY-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3184:
-
Component/s: Services
Affects Version/s: 10.4.0.0
Replication: Connection attempts to
[
https://issues.apache.org/jira/browse/DERBY-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg resolved DERBY-3183.
Resolution: Duplicate
'Error starting tracing' in
[
https://issues.apache.org/jira/browse/DERBY-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Solberg closed DERBY-3183.
--
Closed as duplicate of DERBY-3174
'Error starting tracing' in
[
https://issues.apache.org/jira/browse/DERBY-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2911:
--
Attachment: cleaner.diff
cleaner.tar
I have experimented a little more
[
https://issues.apache.org/jira/browse/DERBY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John H. Embretsen updated DERBY-3187:
-
Derby Info: [Patch Available, Regression] (was: [Regression])
Note: The patch is for
[
https://issues.apache.org/jira/browse/DERBY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John H. Embretsen updated DERBY-3187:
-
Attachment: d3187-v01.diff
Thanks Myrna for clarifying the difference in behavior
[
https://issues.apache.org/jira/browse/DERBY-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541060
]
Bryan Pendleton commented on DERBY-3188:
I saw the same failure on RedHat Linux wiht Sun JDK 1.5.0_05
[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541066
]
Rick Hillegas commented on DERBY-3117:
--
I would appreciate it if people could test-drive the latest patch. I am
New simple demo suitable for supported Java ME platforms
Key: DERBY-3190
URL: https://issues.apache.org/jira/browse/DERBY-3190
Project: Derby
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/DERBY-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541072
]
Rick Hillegas commented on DERBY-3137:
--
Thanks for the new patch, Dag. Looks good to me.
SQL roles: add
I wonder if it would be acceptable to have no security manager for a
server that only accepts connections from localhost, but keep it enabled
if remote connections are enabled.
Kathey
SQL roles: add upgrade support
--
Key: DERBY-3191
URL: https://issues.apache.org/jira/browse/DERBY-3191
Project: Derby
Issue Type: Improvement
Reporter: Dag H. Wanvik
Derby roles introduce a new
[Auto-generated mail]
*Daily* 592816/2007-11-07 18:00:12 CET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0284284 073.16% derbyall
097429742 0 1251.99% suitesAll
linN+1
1
Issue Subscription
Filter: Derby: JIRA issues with patch available (21 issues)
Subscriber: derby-dev
Key Summary
DERBY-3137 SQL roles: add catalog support
https://issues.apache.org/jira/browse/DERBY-3137
DERBY-3109 Nonexistent property derby.database.defaultAccessMode shown
Hi,
does anybody know what causes this?
I am using DITA-OT1.1.2.1.
Thanks,
Dag
[echo] *
[echo] * input =
/export/home/tmp/derby/sb/docs-103/src/ref/refderby.ditamap
[echo] * type = ${transtype}
[echo] *
[
https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541095
]
Mamta A. Satoor commented on DERBY-3172:
After a quick talk with Dan, I realize that the embedded driver
Rick Hillegas wrote:
Unfortunately, this change has proved painful to some users. See, for
instance, DERBY-3086 and the ongoing discussion on DERBY-3083.
DERBY-3086 is simply a bug, inherently it doesn't make the default
installation of a security manager a bad idea. It's just like any other
Rick Hillegas [EMAIL PROTECTED] writes:
I'll admit I am torn about this one. Just summarizing how I
understand it at this point, I don't have a firm opinion.
Cons:
- Changes default behavior (previous Derby versions did not come up
with a default security manager; there was none). Can trip up
[
https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541091
]
Mamta A. Satoor commented on DERBY-3172:
While working on this issue, I found that when a JCBC Connection is
[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541104
]
Thomas Nielsen commented on DERBY-3117:
---
I applied derby-3117-04-propertySetter-ad.diff on WinXP with Suns
I obtained a positive reaction from a group with a large install base
that will be transitioning to version 10.3. Derby and Network Server
are used with sample code and readily available for use as a business
system data store.
The statement I received is:
I am all for it. Anything that
[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541106
]
Thomas Nielsen commented on DERBY-3117:
---
Changing to WinXP, Suns 1.5.0_13 :
---
...
setCompilerProperties:
It looks like something may be wrong with your refderby.ditamap file.
When you run the tail command on it, does the output look something like
this?
If so, see if you have changed something else that might cause that tag
not to be seen.
jdench 100 =tail refderby.ditamap
topicref
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
I am in favor of keeping the current automatic SecurityManager
behavior. I think that the currently-logged issues are fixable.
thanks,
bryan
[
https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541170
]
Kathey Marsden commented on DERBY-3172:
---
I had thought in 10.2 we had changed the client error codes to match
Dag H. Wanvik wrote:
In the final analysis it comes down to what annoys the Derby user
more, a potentially unsafe system or the hassle of dealing with
security. No free lunch...
Though the network server's default installed security manager is a free
lunch for most folks. It provides a more
Rick Hillegas wrote:
Unfortunately, this change has proved painful to some users. See, for
instance, DERBY-3086 and the ongoing discussion on DERBY-3083.
Now that we have some experience with the 10.3 release,
I wonder how much that some experience is? Is there enough to make a
judgment?
Thanks Stan. Just to clarify: your impression was that this group was in
favor of Derby's automatic installation of a security manager?
Thanks,
-Rick
Stanley Bradbury wrote:
I obtained a positive reaction from a group with a large install base
that will be transitioning to version 10.3.
[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541157
]
Thomas Nielsen commented on DERBY-3117:
---
derby-3117-01-propertySetter-ae.diff seems to work fine with WinXP /
[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3117:
-
Attachment: derby-3117-04-propertySetter-ae.diff
Thanks for the quick response, Thomas.
Cache session data in the client driver
---
Key: DERBY-3192
URL: https://issues.apache.org/jira/browse/DERBY-3192
Project: Derby
Issue Type: Improvement
Components: JDBC, Network Client, Network
Mamta A. Satoor (JIRA) [EMAIL PROTECTED] writes:
I forgot to mention that I didn't find any test case in
DataSourceTest.java which will trigger Connection error event. The
existing test cases only test Connection closed event.
It might be good to add a new jira for this improvement if it's
To clarify the statement I received and passed onto the community. The
'positive reaction' was to the OR case:
...Or should we consider turning off this feature in the upcoming 10.3
maintenance release?
With the current behavior (starting the security manager by default),
this group is
[
https://issues.apache.org/jira/browse/DERBY-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541127
]
Daniel John Debrunner commented on DERBY-3086:
--
Rick Is it a bug that sysinfo lives in 3 jars instead
Dag H. Wanvik wrote:
In the final analysis it comes down to what annoys the Derby user
more, a potentially unsafe system or the hassle of dealing with
security. No free lunch...
An aggravating factor on the hassle is, in my experience, the
insufficient tools available for debugging security
[
https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541161
]
Mamta A. Satoor commented on DERBY-3172:
On further investigation, it seems that in client server mode, we
The confusing paragraph is old information and lists the old URL
attribute: /locale=ll_CC/ rather than the new URL attribute
/territory=ll_CC./ This should be corrected and some the behavior it
tries to convey may not have made it into Derby?? The tools guide seems
to have a good
Hi Kim,
Kim Haase [EMAIL PROTECTED] writes:
It looks like something may be wrong with your refderby.ditamap
file. When you run the tail command on it, does the output look
something like this?
Just right, that file ends like this:
topicref href=rrefsqlj12362.dita navtitle=NUMERIC data type
[EMAIL PROTECTED] (Dag H. Wanvik) writes:
topicref href=rrefsqlj12362.dita navtitle=NUMERIC data type class=-
map/topicref
xtrf=/export/home/tmp/derby/sb/docs-103/src/ref/refderby.ditamap
xtrc=topicref:231/topicref
topicref href=rrefsqlj14122.dita navtitle=REAL data type class=-
[
https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541209
]
Dag H. Wanvik commented on DERBY-2914:
--
Patch svn 587668 with log comment:
Derby2914: Added new files and
[
https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541214
]
Bryan Pendleton commented on DERBY-3175:
I propose to submit fixWith3177Case.diff to the trunk fairly soon.
Dag, I am working on DERBY-3172 and as part of that jira entry, I plan
to add test cases for Connection error event.
thanks,
Mamta
On 11/8/07, Dag H. Wanvik [EMAIL PROTECTED] wrote:
Mamta A. Satoor (JIRA) [EMAIL PROTECTED] writes:
I forgot to mention that I didn't find any test case in
[
https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541218
]
Charlie Hubbard commented on DERBY-3175:
I'm actually encountering this issue as well as 1377, but it's
[
https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541221
]
Bryan Pendleton commented on DERBY-3175:
Hi Charlie, thanks for the update! Is there any way for you to
David Van Couvering wrote:
On Nov 8, 2007 12:13 PM, Kathey Marsden [EMAIL PROTECTED]
wrote:
I wonder if it would be acceptable to have no security manager for a
server that only accepts connections from localhost, but keep it enabled
if remote connections are enabled.
I like this, this
[
https://issues.apache.org/jira/browse/DERBY-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3184:
-
Attachment: derby-3184-1.stat
derby-3184-1.diff
The attached patch, v1, adds
Hi,
Thanks for a wonderful database management system.
How do I create custom types in Derby? what would be the formal
approach in creating a geometry type for example?
Im interested as I would love to see Derby with spatial features like
postgis, and Im a postgis programmer.
Regards
Samuel H.
55 matches
Mail list logo