Support "IF [NOT] EXISTS" in CREATE TABLE and "IF EXISTS" in DROP TABLE
-
Key: DERBY-4842
URL: https://issues.apache.org/jira/browse/DERBY-4842
Project: Derby
Issue Ty
[
https://issues.apache.org/jira/browse/DERBY-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920390#action_12920390
]
Dag H. Wanvik edited comment on DERBY-4551 at 10/12/10 6:41 PM:
-
[
https://issues.apache.org/jira/browse/DERBY-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920390#action_12920390
]
Dag H. Wanvik commented on DERBY-4551:
--
You are correct that ssl is not necessary when
[
https://issues.apache.org/jira/browse/DERBY-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920382#action_12920382
]
Dag H. Wanvik commented on DERBY-4841:
--
Seems about right to me.
In the past, I seem
Kathey Marsden writes:
> On 10/12/2010 1:49 PM, Lily Wei wrote:
>
> Hi:
> I intented to announce Apache Derby 10.6.2.1 release with the
> following message.
> If it is okay with everybody, I will send it soon.
>
>
> Lily, I think it looks fine. Tiny nit, I would say tri
On 10/12/2010 1:49 PM, Lily Wei wrote:
Hi:
I intented to announce Apache Derby 10.6.2.1 release with the
following message.
If it is okay with everybody, I will send it soon.
Lily, I think it looks fine. Tiny nit, I would say triggers instead of
trigger.
Without wonderful Derby
[
https://issues.apache.org/jira/browse/DERBY-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen reassigned DERBY-1963:
-
Assignee: Knut Anders Hatlen
> Routine parameter names displayed by dblook are no
[
https://issues.apache.org/jira/browse/DERBY-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-1963:
--
Attachment: d1963.diff
dblook uses the ALIASINFO column in SYS.SYSALIASES to produce th
[
https://issues.apache.org/jira/browse/DERBY-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-4741:
-
Attachment: derby-4741-nio-container+log+waits+locks-2.stat
derby-4741-nio-contain
Hi:
I intented to announce Apache Derby 10.6.2.1 release with the following
message.
If it is okay with everybody, I will send it soon.
Without wonderful Derby group, this can never be done. Derby will have many
great releases to come.
===
[
https://issues.apache.org/jira/browse/DERBY-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920336#action_12920336
]
Tiago R. Espinha commented on DERBY-4836:
-
I would think that despite it throwing a
Hi Rick:
Thank you for the detail information. I was getting confused. However, I
found the information with Publication page now.
I will proceed with Publication with 10.6.2.1 release.
Sincerely,
Lily
From: Rick Hillegas
To: derby-dev@db.apache.
Lily Wei wrote:
Hi there:
I am in the step 6 of after a successful vote to wrap up the
10.6.2.1 release.
For some reasons, I could note find the step I was at from the
DerbySnapshotOrRelease anymore.
How could find the old page again?
Thanks,
Lily
Hi Lily,
My apologies. I am revam
[
https://issues.apache.org/jira/browse/DERBY-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920303#action_12920303
]
Thomas Hill commented on DERBY-4551:
Would need advice on a related question:
At this s
Hi there:
I am in the step 6 of after a successful vote to wrap up the 10.6.2.1
release.
For some reasons, I could note find the step I was at from the
DerbySnapshotOrRelease anymore.
How could find the old page again?
Thanks,
Lily
I have created DERBY-4841 to track our attempts to clean up the public
api of our top level ant build script. After checking in a patch on that
issue, here is the new public api which you see when you type "ant
-projecthelp":
Main targets:
all Compile all of the source, including tests as wel
[
https://issues.apache.org/jira/browse/DERBY-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920248#action_12920248
]
Dag H. Wanvik commented on DERBY-4741:
--
Lily, I looked at derby.log: The stack trace y
[
https://issues.apache.org/jira/browse/DERBY-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4841:
-
Attachment: derby-4841-01-aa-ricksPicks.diff
Attaching derby-4841-01-aa-ricksPicks.diff. This adj
[Auto-generated mail]
*Daily* 1021397/2010-10-11 18:00:20 MEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
NA NA NANA suitesAll
NA NA NANA jdbcapiAutoLoad
NA
Improve projecthelp for the top level Derby build script
Key: DERBY-4841
URL: https://issues.apache.org/jira/browse/DERBY-4841
Project: Derby
Issue Type: Improvement
Componen
[
https://issues.apache.org/jira/browse/DERBY-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-2573:
-
Attachment: derby-2573-07-aa-createBranch.diff
Attaching derby-2573-07-aa-createBranch.diff. This
[
https://issues.apache.org/jira/browse/DERBY-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920225#action_12920225
]
Dag H. Wanvik commented on DERBY-4741:
--
Thanks, Knut and Lily.
Ok, good to know that
Hi Kristian:
Thank you so much for generating the Maven artifacts for Derby 10.6.2.1.
It
looks like it did not propagated to the Maven repositories yet. I will keep
verifying and keep going from there for Derby 10.6.2.1 release.
I will help out figuring out how to setup a pure Windows
[
https://issues.apache.org/jira/browse/DERBY-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920218#action_12920218
]
Lily Wei commented on DERBY-4741:
-
Hi Dag:
Thank you. I am so exciting to help out tes
Rick Hillegas writes:
> Knut Anders Hatlen wrote:
>> Rick Hillegas writes:
>>
>>
>>> I agree that most developers won't care about this file. It is
>>> interesting archeology for release managers, though.
>>>
>>
>> The most interesting thing in the list is that the 10.5.3.0 artifacts
>>
Knut Anders Hatlen wrote:
Rick Hillegas writes:
I agree that most developers won't care about this file. It is
interesting archeology for release managers, though.
The most interesting thing in the list is that the 10.5.3.0 artifacts
are broken, and that 10.5.3.0_1 should be used ins
[
https://issues.apache.org/jira/browse/DERBY-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920186#action_12920186
]
Knut Anders Hatlen commented on DERBY-4741:
---
Hi Dag,
There's some discussion abo
Rick Hillegas writes:
> I agree that most developers won't care about this file. It is
> interesting archeology for release managers, though.
The most interesting thing in the list is that the 10.5.3.0 artifacts
are broken, and that 10.5.3.0_1 should be used instead. I think this is
something th
[
https://issues.apache.org/jira/browse/DERBY-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-1439:
--
Attachment: patch1.diff
I tried the naive approach to removing AntiGC (see the attached
Hi Kristian,
I cast my vote for lightweight processes. Of these choices, option (c)
sounds best to me.
Even better and lighterweight would be to separate this log into its own
file. The maven script could automatically add an entry to the end of
this log every time a release is published. Th
[
https://issues.apache.org/jira/browse/DERBY-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920177#action_12920177
]
Dag H. Wanvik commented on DERBY-4741:
--
Hi Lily, thanks for test driving the patches :
Issue Subscription
Filter: Derby: JIRA issues with patch available (8 issues)
Subscriber: derby-dev
Key Summary
DERBY-4741 Make Derby work reliably in the presence of thread interrupts
https://issues.apache.org/jira/browse/DERBY-4741
DERBY-268 Add Support for truncat
Kristian Waagan writes:
> Hi,
>
> When I worked on the scripts generating and publishing the Maven 2
> artifacts, I added a release history to the maven2/README.txt
> file. This file exists on every branch.
> I did not think a lot about how this would work out as we publish new
> releases. Its o
Hi,
When I worked on the scripts generating and publishing the Maven 2
artifacts, I added a release history to the maven2/README.txt file. This
file exists on every branch.
I did not think a lot about how this would work out as we publish new
releases. Its only purpose is to serve as a record
On 11.10.10 15:40, Lily Wei wrote:
Hi Kristian:
It is so good to hear from you.
Thank you for the detail information.
I went ahead and start the process on 'mvn clean install'. As you
correctly point out, it
will not work due to not setting up properly for the username. I try a
lot of way
35 matches
Mail list logo
