[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6945:
---
Attachment: weirdAnt.out
> Re-package Derby as a collection of jigsaw modu
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376184#comment-16376184
]
Bryan Pendleton commented on DERBY-6945:
Good news! It seems that the only regression test that's
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376176#comment-16376176
]
Bryan Pendleton commented on DERBY-6945:
Thanks Rick!
Let me try to gather more information.
I
Hi Rahul,
These pages are a good place to start:
http://db.apache.org/derby/derby_comm.html
https://wiki.apache.org/db-derby/DerbyDev
thanks,
bryan
On Sun, Feb 25, 2018 at 8:19 AM, Rahul Chhabra wrote:
> Hey guys!
> I really want to contribute to Derby.
> Where do
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375894#comment-16375894
]
Bryan Pendleton commented on DERBY-6945:
Hi Rick, a 3rd question: do you know if we are regularly
Hi Derby developers,
I'm staring at this code in NetworkServerControlImpl.java;
private void writeShort(int value) throws Exception
{
try {
commandOs.writeByte((byte)((value & 0xf0) >> 8 ));
commandOs.writeByte((byte)(value & 0x0f));
}
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375690#comment-16375690
]
Bryan Pendleton commented on DERBY-6945:
A kind-of related question:
When I have a syntax error
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375687#comment-16375687
]
Bryan Pendleton commented on DERBY-6945:
Hey Rick, I apologize, I've been sort of drifting
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6981.
Resolution: Fixed
Assignee: Bryan Pendleton
Fix Version/s: 10.15.0.0
Thanks
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348037#comment-16348037
]
Bryan Pendleton commented on DERBY-6981:
Attached 'patch1.diff' is a patch proposal, containing
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6981:
---
Attachment: patch1.diff
> SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerExceptionXJ00
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348010#comment-16348010
]
Bryan Pendleton commented on DERBY-6981:
I don't fully understand what's going wrong here, but I
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346918#comment-16346918
]
Bryan Pendleton commented on DERBY-6981:
Yes, it reproduces for me now. I see the following in my
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346277#comment-16346277
]
Bryan Pendleton commented on DERBY-6981:
I took the provided derby-test.java and tweaked
[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6981:
---
Attachment: test1.java
> SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerExceptionXJ00
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308145#comment-16308145
]
Bryan Pendleton commented on DERBY-6945:
Yes that helps.
I was confused about whether
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307500#comment-16307500
]
Bryan Pendleton commented on DERBY-6945:
I like the idea of putting the external JDBC driver
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307285#comment-16307285
]
Bryan Pendleton commented on DERBY-6945:
Thank you Rick, for the detailed and very useful progress
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306357#comment-16306357
]
Bryan Pendleton commented on DERBY-6945:
Hi Rick,
If you were to step back, at this point
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303982#comment-16303982
]
Bryan Pendleton commented on DERBY-6945:
Rick, in these reflection/delegation approaches you're
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297827#comment-16297827
]
Bryan Pendleton commented on DERBY-6945:
Hi Rick, thanks for the follow-up. From some casual web
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296884#comment-16296884
]
Bryan Pendleton commented on DERBY-6945:
No, I don't think you've misunderstood me. I just thought
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296067#comment-16296067
]
Bryan Pendleton commented on DERBY-6945:
Hi Rick, thanks for the thorough explication
Hi Rick,
I'm continuing to try to follow along, though I confess I'm lagging a
little bit.
Can you expand on this section a little bit:
> M
> java/testing/org/apache/derbyTesting/functionTests/harness/FileCompare.java
> M
>
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292607#comment-16292607
]
Bryan Pendleton commented on DERBY-6945:
It feels right, to me, to have sysinfo in derbytools
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288585#comment-16288585
]
Bryan Pendleton commented on DERBY-6945:
Hi Rick,
Since I'm still learning about Jigsaw, expect
[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280269#comment-16280269
]
Bryan Pendleton commented on DERBY-6809:
Changes to the code, unless they are emergency bug fixes
[
https://issues.apache.org/jira/browse/DERBY-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278725#comment-16278725
]
Bryan Pendleton commented on DERBY-6972:
Try running your program under the debugger, and set
[
https://issues.apache.org/jira/browse/DERBY-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277974#comment-16277974
]
Bryan Pendleton commented on DERBY-6972:
Or try 'strace' (Linux) or 'Process Monitor' (Windows
[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275359#comment-16275359
]
Bryan Pendleton commented on DERBY-6809:
Oh, I think we could make a stronger statement than
[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272769#comment-16272769
]
Bryan Pendleton commented on DERBY-6979:
It seems like an interesting suggestion to me. I would
On Sat, Nov 25, 2017 at 4:00 PM, Rick Hillegas wrote:
> My last comment on https://issues.apache.org/jira/browse/DERBY-6945 proposes
> how we could decompose Derby into Jigsaw-ready modules.
Thanks for pushing forward with this, Rick!
Your writeup and your references to
> Afer that worked, I replaced "jdbc:derby:memory:db" with
> "jdbc:derby://localhost:1527/demo4" and got the exception I'm pasting below
> this. I don´t know what I'm configuring wrong.
> Exception in thread "main" java.sql.SQLSyntaxErrorException:
> 'SYSCS_UTIL.SYSCS_CREATE_USER' no se reconoce
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252800#comment-16252800
]
Bryan Pendleton commented on DERBY-6974:
Yes, perfect. Thank you very much for the extra
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251464#comment-16251464
]
Bryan Pendleton commented on DERBY-6974:
How does changing our minimum compiler level for Ant
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249085#comment-16249085
]
Bryan Pendleton commented on DERBY-6977:
We used to have very odd, unreproducible test problems
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248586#comment-16248586
]
Bryan Pendleton commented on DERBY-6977:
Would it help to force the new UUID value to uppercase
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248297#comment-16248297
]
Bryan Pendleton edited comment on DERBY-6977 at 11/11/17 4:02 AM:
--
Cool
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248297#comment-16248297
]
Bryan Pendleton commented on DERBY-6977:
Wow it's crazy that we never saw this before.
I read
>> Here, I see that to support Java 9, we need JaCoCo 0.7.8:
>> https://groups.google.com/forum/#!msg/jacoco/Zf0Cwj13G2g/wpyrYAEECAAJ
>
> If I understand that script, our JaCoCo runs rely on an old JaCoCo version
> cached on Kristian's Apache website. Here are some things we could do:
>
> 1) Ask
[
https://issues.apache.org/jira/browse/DERBY-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239681#comment-16239681
]
Bryan Pendleton commented on DERBY-2925:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010
Bryan Pendleton created DERBY-6976:
--
Summary: Update JaCoCo Jenkins artifacts for Java 9 support
Key: DERBY-6976
URL: https://issues.apache.org/jira/browse/DERBY-6976
Project: Derby
Issue
> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-JaCoCo/49/
This build correctly used Java 9.
But it did not run successfully.
I filed https://issues.apache.org/jira/browse/DERBY-6976 to track
this, with the following description:
The output said things like:
[java] Java
The Derby-Trunk build seemed to work OK (Rick can you verify?) so I
made the corresponding change to the Derby-trunk-suites.All and
Derby-trunk-JaCoCo jobs and submitted them, too:
https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/130/
Hi Rick,
I found a drop list in the "configure" screen under "General" where I
could pick a JDK, and I picked "JDK 1.9 latest".
I ran another build: https://builds.apache.org/job/Derby-trunk/2513/
Let's keep an eye on this build and see how it behaves.
thanks,
bryan
> I have tried compiling the insane, production engine at debug level
> "lines,source".
> I think that the expense is worth paying in order to gain the
> benefit of more useful stack traces.
+1. Improved supportability and field diagnosis is a big benefit for me.
bryan
> As PMC chair could you grant me access to Jenkins so that I can explore how
> to make this change?
Hi Rick,
I think this is done ... can you check?
thanks,
bryan
Hi Rick,
What do we need to do with our Apache-hosted Jenkins build runs?
Presumably, the Jenkins builds of main should use Java 9.
The Jenkins builds of older branches should use the appropriate Java version.
Have you already taken care of this?
thanks,
bryan
> Let me know if I should hold off doing this. Once I check in the changes,
> you will no longer be able to use JDK 8 in order to build Derby. Instead,
Hi Rick, two clarifying questions:
1) This will only affect the trunk, not any of the current release branches?
2) Not only will we need to
[
https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214373#comment-16214373
]
Bryan Pendleton commented on DERBY-6970:
What is the exact exception that you get when you receive
Thanks Rick!
I am, indeed, running Forrest 0.9, so I guess that's why I didn't have
that problem on my builds.
The thing about only doing releases infrequently is that little
details like this slip my mind. Thanks for updating the documentation,
that's incredibly helpful for the next time
I see the same behavior, Rick.
I don't immediately see what's wrong.
That entire mirror distribution system is pretty opaque to me.
Perhaps you should ping infra@ ?
bryan
The release announcement looks great!
I don't recall the details of how (or even if) I posted to announce@
for 10.13. Did you happen to search the archives to see if a mail from
me went out during that release, and, if so, which account I used to
send it?
thanks,
bryan
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196319#comment-16196319
]
Bryan Pendleton commented on DERBY-6968:
That patch looks fine to me, thanks for taking care
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16195790#comment-16195790
]
Bryan Pendleton commented on DERBY-6968:
Our results aren't ordered at all? Or they are only
On Wed, Sep 20, 2017 at 5:42 AM, Rick Hillegas
wrote:
> Please test-drive the 10.14.1.0 candidate, then vote on whether to accept
> it as a Derby release.
>
>
+1
I have successfully used the release candidate with Java 8 on Windows 10,
Fedora 26, and Ubuntu 16.04
[
https://issues.apache.org/jira/browse/DERBY-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6965.
Resolution: Fixed
Fix Version/s: 10.15.0.0
The updated pages appear to be showing up
[
https://issues.apache.org/jira/browse/DERBY-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6965:
---
Attachment: siteDocs.diff
derby_comm.html
derby_source.html
[
https://issues.apache.org/jira/browse/DERBY-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6904.
Resolution: Fixed
Fix Version/s: 10.14.1.0
We have no further work planned
[
https://issues.apache.org/jira/browse/DERBY-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6905.
Resolution: Fixed
The test suites appear to have been stable since our last commit
Thank you for working on Derby!
However, suggesting a change to Derby by posting a screenshot of code is
not the right process to use.
For a variety of reasons, both technical and non-technical, we have a very
specific process to use for making changes to Derby, and it is described
here:
Thank you for working on Derby!
However, suggesting a change to Derby by posting a screenshot of code is
not the right process to use.
For a variety of reasons, both technical and non-technical, we have a very
specific process to use for making changes to Derby, and it is described
here:
Thank you for working on Derby!
However, suggesting a change to Derby by posting a screenshot of code is
not the right process to use.
For a variety of reasons, both technical and non-technical, we have a very
specific process to use for making changes to Derby, and it is described
here:
Bryan Pendleton created DERBY-6965:
--
Summary: Community page describing contribution process has stale
testing section
Key: DERBY-6965
URL: https://issues.apache.org/jira/browse/DERBY-6965
Project
Rick, where do I find the instructions about how to run regression tests
using only the jars in the distribution? I kinda sorta vaguely remember how
to do this, but I hunted around the wiki and elsewhere and couldn't find a
nice clean set of instructions.
Meanwhile, I:
- verified the signatures
Are you asking how to reproduce the problem on your computer?
Or are you asking how best to go about fixing the problem?
thanks,
bryan
On Mon, Sep 25, 2017 at 10:43 AM, Indumini Ayomi
wrote:
> Hello,
>
> I am studying about issue #6909. But I don't have exact idea
The crucial difference between using String, and using char[], is that the
String cannot be changed after we are done using it, while the char[] array
can be changed once we are done using it.
So it's not *just* changing from String to char[], it's *also* clearing the
character array after we are
Hi Rick,
I was "off the grid" this weekend.
Thanks for pulling the release together, right on time.
I'm hoping to find some time to dig into the release candidate, but I've
got to dig out from a pile of Other Stuff.
I'm anticipating getting some time to independently validate the release on
my
Hi Rick, I had this same problem. It's "home.apache.org" now. Please read
the updates I made to
https://wiki.apache.org/db-derby/ReleaseCandidates#Post_the_release_artifacts
carefully, and you'll see what worked for me.
bryan
[
https://issues.apache.org/jira/browse/DERBY-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170058#comment-16170058
]
Bryan Pendleton commented on DERBY-6957:
Which other code is calling DROP TABLE,and what else
[
https://issues.apache.org/jira/browse/DERBY-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169532#comment-16169532
]
Bryan Pendleton commented on DERBY-6961:
Thanks Rick! It's good to see that it was more-or-less
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169336#comment-16169336
]
Bryan Pendleton commented on DERBY-6395:
I am not sure what is wrong. You should NOT need
[
https://issues.apache.org/jira/browse/DERBY-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169126#comment-16169126
]
Bryan Pendleton commented on DERBY-6962:
Thanks Rick!
The only tiny, tiny nit I see
[
https://issues.apache.org/jira/browse/DERBY-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-4041:
---
Attachment: commentedQueryRepro.sql
commentedQueryRepro.out
Hi Dimuthu,
I
[
https://issues.apache.org/jira/browse/DERBY-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164095#comment-16164095
]
Bryan Pendleton commented on DERBY-4041:
Thanks for the updated information. I will try
[
https://issues.apache.org/jira/browse/DERBY-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164078#comment-16164078
]
Bryan Pendleton commented on DERBY-6961:
Thanks for catching this, Rick.
I definitely don't think
[
https://issues.apache.org/jira/browse/DERBY-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160386#comment-16160386
]
Bryan Pendleton commented on DERBY-6958:
Thanks for the thorough catalog of items.
Even if we
[
https://issues.apache.org/jira/browse/DERBY-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160122#comment-16160122
]
Bryan Pendleton commented on DERBY-6941:
Yes, I like the new downloads page a lot. Thanks
[
https://issues.apache.org/jira/browse/DERBY-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157948#comment-16157948
]
Bryan Pendleton commented on DERBY-4041:
Thank you for investigating this issue! But I'm not sure
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156351#comment-16156351
]
Bryan Pendleton commented on DERBY-6395:
Thanks for the update, and thanks for your work
[
https://issues.apache.org/jira/browse/DERBY-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156337#comment-16156337
]
Bryan Pendleton commented on DERBY-6957:
Can you isolate this to a standlone test case
>
> Thanks for raising this issue. Here's a thought: On the download page,
> instead of dividing releases into the "Latest Official Releases" and
> "Archived Official Releases" blocks, we could divide the releases into
> blocks identified by the oldest JVM which supports them.
>
>
>
I like this
The release notes look great, Rick, thanks for moving this along.
And the schedule is still OK for me, too.
Regarding the release notes, I wonder if we've called enough attention to
the Java 8 notification at the end of the "Overview" section.
It seems clear enough, I'm just wondering if
Thank you for doing that testing!
Perhaps the problem described by DERBY-6711 has already been fixed? It is a
slightly old issue, and perhaps it was fixed but not marked as fixed?
Do you see any occurrences of the message in question, but with the
database name properly filled in, in your logs?
The DERBY-6814 description is confusing. I am not certain what problem is
being described by that JIRA Issue.
I think that some experimentation is necessary to see if you can reproduce
the problem.
Here is a good web page which describes how to use the JMX integration
features of Derby, and
Have you tried running the Derby replication tests, as described here:
https://issues.apache.org/jira/browse/DERBY-6711?focusedCommentId=16100848=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16100848
thanks,
bryan
Perhaps you could open the appropriate JIRA issues (to add documentation;
to add additional data types; etc.) as sub-tasks of this JIRA issue, to
help us keep track of it all?
[
https://issues.apache.org/jira/browse/DERBY-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142950#comment-16142950
]
Bryan Pendleton commented on DERBY-6942:
I think it would be fine to add additional data types
Hmmm... Does this mean that the central Subversion repository is out of
disk space?
Or does it mean that the local disk on the Jenkins worker machine is out of
disk space?
bryan
-- Forwarded message --
From: Apache Jenkins Server
Date: Sun, Aug 20,
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134498#comment-16134498
]
Bryan Pendleton commented on DERBY-6395:
Can you please use the commands which are described here
[
https://issues.apache.org/jira/browse/DERBY-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134493#comment-16134493
]
Bryan Pendleton commented on DERBY-6909:
That is correct; the query "select * from TEST
I've completed all the work I intend for this. Thanks for the quick work on
this! +1 to resolve and include in this fall's release.
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6956:
---
Attachment: withTest.diff
Hi Rick, attached 'withTest.diff' includes a few new test cases
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128149#comment-16128149
]
Bryan Pendleton commented on DERBY-6956:
Thanks for the patch, Rick. I agree with your assessment
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127293#comment-16127293
]
Bryan Pendleton commented on DERBY-6956:
It's not clear to me why we make this check for CREATE
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126786#comment-16126786
]
Bryan Pendleton commented on DERBY-6956:
To summarize: my opinion is that DERBY-836 and DERBY-2605
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126784#comment-16126784
]
Bryan Pendleton commented on DERBY-6956:
I suspect that this code in sqlgrammar.jj is the source
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126781#comment-16126781
]
Bryan Pendleton commented on DERBY-6956:
The stack trace at the moment that CREATE TABLE AS SELECT
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126715#comment-16126715
]
Bryan Pendleton commented on DERBY-6956:
And in the particular code path tickled by the CREATE
[
https://issues.apache.org/jira/browse/DERBY-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126710#comment-16126710
]
Bryan Pendleton commented on DERBY-6956:
DataTypeDescriptor.isUserCreatableType was added by DERBY
301 - 400 of 4629 matches
Mail list logo