Hi
Can some one grant me developer status in jira ? I plan to submit some
patches in few days.
My jira id is anurag
thanks
anurag
classes support in Embedded driver
Key: DERBY-819
URL: http://issues.apache.org/jira/browse/DERBY-819
Project: Derby
Type: Sub-task
Components: JDBC
Environment: all
Reporter: Anurag Shekhar
Assignee:
Hi David
I will made the changes.
please see inline
thanks
anurag
David Van Couvering (JIRA) wrote:
- Why do you set the territory to en_US?
I am printing the message so in case the default locale is not the same
as I used to generate the original out file it will fail. So I am
setting te
dcode it in the tests. Anurag, have you tried this?
>
> Thanks,
>
> David
>
> Knut Anders Hatlen wrote:
> > "David W. Van Couvering" <[EMAIL PROTECTED]> writes:
> >
> >
> >>Anurag Shekhar wrote:
> >>
> >>>Hi Davi
o be no help here. Section 20.2.2.1 has this sentence:
"If the JDBC driver does not provide its
own implementation of a QueryObjectGenerator, it must invoke the default
QueryObjectGenerator implementation provided by Java SE 6."
I can't see any mention of how a driver implementation finds the
Three months ago, we shelved this topic, promising to return to it
later. I would like to reach consensus on this problem now. In a
nutshell: JDBC4 introduces new methods whose signatures contain
generics. Because of this, DataSource implementations can't satisfy both
the JDBC3 and JDBC4 contrac
-1
The use of InternalDriver.activeDriver() to obtain a factory exposes Derby to
potential NullPointerExceptions in a shutdown or error on boot situation. I see
that you saw one in your testing as you have a comment on that in the shutdown
code. Such NPEs will hide the real error from users,
Looks like we already have some problem.
org.apache.derby.iapi.sql.conn.ConnectionUtil.getCurrentLCC throws
SQLException
with status set as SQLState.NO_CURRENT_CONNECTION (0803). It doesn't use
Util and constructs the SQLException directly.
Changing this to use Util is the easy part but this sta
Would it be acceptable for there to continue to be a static method in
Util that worked as it does today, always returning a
java.sql.SQLException? This method would have sanity checks to ensure
that the SQLState passed in did not start wiht any of the special values
that require specific sub-cla
Hi, Anurag, this sounds interesting, I generally like this kind of
approach over creating hardcoded specific SQLException classes in our
code. We should be able to solve this in a way that is less hardcoded
and more flexible, which is always good for long-term maintainability.
I don't quite
- If I have this right, the exceptionFactory doesn't get initialized until the
first instance of InternalDriver() is created. Isn't it possible that
getExceptionFactory() will return null? Doesn't this mean that at some point
during pre-boot I'll get a NullPointerException if I try to thro
Dan, what's your status with this patch? As it stands your -1 is
still holding it back.
This is not the complete patch i will posting is shortly
Link to jdbc 4 spec and api downloads
http://java.sun.com/products/jdbc/download.html#corespec40
anurag
exception
anurag
David W. Van Couvering wrote On 02/13/06 23:55,:
I concur, the network client should *not* be using
Util.notImplemented(), and this needs to be fixed.
David
Daniel John Debrunner wrote:
Anurag Shekhar (JIRA) wrote:
Thus it seems the changes you are making related to not
What's the benefit of having the embedded driver not call the
Util.notImplemented() method and thus increasing the footprint for no value?
Wouldn't fixing the client's use first make sense? Then the
Util.notImplemented() method could remain.
Dan.
I have added a new issue and attached a pat
shorthand methods.
David
NetClient JDBC (40) using engine classes
Key: DERBY-983
URL: http://issues.apache.org/jira/browse/DERBY-983
Project: Derby
Type: Bug
Components: Network Client
Environment: all
Reporter: Anurag Shekhar
URL: http://issues.apache.org/jira/browse/DERBY-819
Project: Derby
Type: Sub-task
Components: JDBC
Environment: all
Reporter: Anurag Shekhar
Assignee: Anurag Shekhar
Priority: Minor
Attachments: .derby-819_2.stat, derby-819-onlyforreview.diff, derby-819.diff,
derby-819_2
Index: java/engine/org/apache/derby/impl/jdbc/EmbedConnection40.java
===
--- java/engine/org/apache/derby/impl/jdbc/EmbedConnection40.java
(revision 380197)
+++ java/engine/org/apache/derby/impl/jdbc/EmbedConnection40.java
.
Add JDBC4 Ease of Development Support
-
Key: DERBY-942
URL: http://issues.apache.org/jira/browse/DERBY-942
Project: Derby
Type: New Feature
Components: JDBC
Reporter: Rick Hillegas
Assignee: Anurag Shekhar
Fix For
Hi
I am trying to locate DataFactory from the moniter when i call
Monitor.getMonitor().findService (DataFactory.MODULE, "databasename")
It returns me an instance of org.apache.derby.impl.db.BasicDatabase
Am I doing something wrong here ? Or its expected behavior ? In that
case how to i get the
Let me explain why I need a temporary file. I need a storage where
blob/clob can be stored before writing into the table. As the size of
lob can go upto 2gb its not possible to keep it in memory. I am using
the temporary file to keep the byte/string in case the the size grows
more than 4k.
So
) Monitor.findServiceModule(o,
DataFactory.MODULE);
anurag
Anurag shekhar wrote:
Hi
I am trying to locate DataFactory from the moniter when i call
Monitor.getMonitor().findService (DataFactory.MODULE, "databasename")
It returns me an instance of org.apache.derby.impl.db.BasicData
Daniel John Debrunner wrote:
Anurag shekhar wrote:
Let me explain why I need a temporary file. I need a storage where
blob/clob can be stored before writing into the table. As the size of
lob can go upto 2gb its not possible to keep it in memory. I am using
the temporary file to keep the
Mike Matrigali wrote:
Anurag shekhar wrote:
Let me explain why I need a temporary file. I need a storage where
blob/clob can be stored before writing into the table. As the size of
lob can go upto 2gb its not possible to keep it in memory. I am using
the temporary file to keep the byte
inue to get security exception while creating a temporary file.
But when I add same permission to all (grant {}) it works fine.
What am i doing wrong here ?
thanks
anurag
Daniel John Debrunner wrote:
Anurag Shekhar wrote:
Yes java.io.File.createTempFile() will work. But is it ok to grant fi
derby-1341 is only for Embedded Driver.
anurag
Mike Matrigali wrote:
Suresh Thalamati wrote:
Anurag shekhar wrote:
I need to grant derby.jar read,write,delete access on tmp directory
(issue derby-1341).
I tried adding
permission java.io.FilePermission "${java.io.tmpdir}${/}-&qu
I can use database tmp file system. I can get the tmp directory name
from StorageFactory. Or is there some better way of getting this directory ?
anurag
Suresh Thalamati wrote:
Anurag shekhar wrote:
I need to grant derby.jar read,write,delete access on tmp directory
(issue derby-1341).
I
a good first step to
minimize the number of jdk16 canons...
Myrna
On 3/16/06, *Anurag Shekhar (JIRA)* <mailto:derby-dev@db.apache.org>> wrote:
[ http://issues.apache.org/jira/browse/DERBY-1105?page=all
<http://issues.apache.org/jira/browse
This was a bug in jdk1.6 (mustang) it was fixed in build 74.
anurag
David W. Van Couvering wrote:
When I run the jdbc40 test suite, I get this error (most times). Is
anyone else seeing this?
Exception in thread "main" java.lang.IllegalArgumentException:
Timestamp format
must be -mm-dd h
Also, I think this also indicates that we should consider using
delegation instead of inheritance for code reuse.
Andreas
I didn't get it, how does it indicates that ?
anurag
but I
don't think making a design decision in anticipation of programing
mistakes is a good idea.
anurag
interface
Andreas Korneliussen wrote On 03/28/06 17:54,:
Anurag Shekhar wrote:
Also, I think this also indicates that we should consider using
delegation instead of inheritance for
Daniel John Debrunner wrote On 04/10/06 23:54,:
In the properties file for the TestQueryObject JDBC 4.0 test we have:
#this case tests QueryObject related methods which are present in jdk 1.6
#default QueryObjectGenerator uses reflection to check the Data Object
#before calling the methods to
[X] +1 Make Andreas Kornelliusen a committer for Derby
anurag
[X] +1 Make Suresh Thalamati a committer for Derby
anurag
Hi
I am trying to implement set methods for blob and clob in embedded
driver (derby-1341).
I plan to use tmp file system as temporary storage in case user pushes
in data more than
MAX_BUF.
can some some one point me to right doc where I should be looking for
this information ?
I know that Sto
Hi Myrna
I have two patches under review (2247 and 2379).
Apart from these two I am working one three more issue
1. 2694
I have a patch for it but I need to run the junit tests and write a
reproducible test for the same.
I will be creating two more jira issue
1. An offshoot of 2586 : To ensur
While debugging for DERBY-2694 I noticed
client code is getting a truncated string. It was of length 10900 chars
in original code and 10899 chars after applying the patch, but the
function is returning string of 2 chars. I have attached class to
reproduce this in DERBY-2694. Can some one ple
Hi
ij> SELECT * FROM t ORDER BY key_col;
KEY_COL|DESC_COL |TS_STRING |TS
---
1 |NULL |2017-03-12 01:48:00.000
Daniel John Debrunner wrote:
Oystein Grovlen - Sun Norway wrote:
Daniel John Debrunner (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465625
]
Daniel John Debrunner commented on DERBY-2247:
--
t from the
fields participating in unique constraint (to achieve new behaviou from
the existing constraints) .
Anurag Shekhar (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated
ist should only be on non-nullable columns
so should not need to be changed. I have not read through the new
code yet, but I assume also that new constraints on non-nullable columns
also don't use the "new" code - they should not pay the left/right
search cost.
Anurag Shekh
Army wrote:
Mike Matrigali wrote:
This would mean either dropping/recreating the index at alter time or
adding a new store interface to "convert" from old index type to new
index type.
I haven't been following this discussion at all, but for what it's
worth, this same sort of question came up
Mike Matrigali wrote:
Anurag shekhar wrote:
Army wrote:
Mike Matrigali wrote:
This would mean either dropping/recreating the index at alter time or
adding a new store interface to "convert" from old index type to new
index type.
I haven't been following this discussion at al
Army wrote:
I haven't been following this discussion at all, but for what it's
worth, this same sort of question came up in the context of
DERBY-3299. I went with the simple approach of dropping the old index
and creating the new one, so some logic for that kind of thing is now
in the 10.4
[EMAIL PROTECTED] wrote:
... is fast approaching (2008-02-29)
Is this still a reasonable date, or should we consider delaying it?
Unique constraints On track
I have all the patches (3 of them) in jira and there are chances that
they might get commited before 29th but having one more
cised if the index is accessed for the first
time, as the contain information is otherwise cached. It is important
to test that the new formatid stuff is being read from DISK correctly.
Also how have you been testing your retry code?
Anurag Shekhar (JIRA) wrote:
[
https://issues.apach
unique constraint on non-nullable columns would be unchanged. So this
constraint should still be backed by a unique index.
Anurag Shekhar (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedComme
Neighter the sql spec nor the derby manual promises this behavior
(ordering of group by
clause without order by). So I don't think this is a deviation from the
existing behavior.
anurag
Anurag shekhar wrote:
Unique constraint on non nullable fields still act like a unique index
(because
nique
constraint.
o future index optimization may not apply, there are some compression
techniques that lend themselves better to unique indexes vs.
non-unique.
o others i have not thought of.
Anurag shekhar wrote:
Unique constraint on non nullable fields still act like a unique
index (because the
I am seeing some failures in LangScripts tests in my fresh workspace.
Is some one else also experiencing failures ?
I am running SUN jdk1.6 on linux.
thanks
anurag
After enabling unique constraint on nullable fields db2
compatibility tests are failing because they expect failure while
creating unique constraint over null able fields.
For now I have modified the out file (Attached separately in DERBY-3330,
db2Compatibility.diff )
Is it right thing to do ? o
you can find few papers on store here
http://db.apache.org/derby/papers/index.html#Derby+Engine
anurag
那贵鹏 wrote:
hi,may I ask something about store layer of Derby?
I want to learn the architecture of store layer .
for Example, Class Diagram and relations and how the data is stored in
what kin
File is now in. Please update the workspace.
anurag
Rick Hillegas wrote:
I am seeing the following build failure after syncing with the trunk.
It looks like a test class was not checked in:
[javac]
/Users/rh161140/derby/mainline/trunk/java/testing/org/apache/derbyTesting/functionTests/test
you should add a new error message for
the new code to use, and soft upgrade can continue to use
the old message. This is assuming there is no SQL standard for this
exact error number.
Anurag Shekhar (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-3456?page
---
Key: DERBY-3523
URL: https://issues.apache.org/jira/browse/DERBY-3523
Project: Derby
Issue Type: Bug
Affects Versions: 10.4.0.0, 10.5.0.0
Reporter: Anurag Shekhar
It might be because of my work related to unique constraint, I will look
into it.
anurag
Kathey Marsden (JIRA) wrote:
In 10.4 soft upgrade mode I cannot:
ij> create table t0 (i int not null, v varchar(1) not null, constraint uq
unique(v,i));
0 rows inserted/updated/deleted
ij> alter table t
Bryan Pendleton wrote:
I propose that Thomas Nielsen shall be a Derby committer.
+1
Rick Hillegas wrote:
Please vote on whether we should make V. Narayanan a Derby committer.
The polls close at 5:00 pm San Francisco time on Thursday April 10.
+1
Rick Hillegas wrote:
Please vote on whether we should make Jørgen Løland a Derby committer.
The polls close at 5:00 pm San Francisco time on Thursday April 10.
+1
What else are people planning to do for the next feature release?
I am planning to work on support for duplicate nulls in unique index.
https://issues.apache.org/jira/browse/DERBY-2212
thanks
anurag
QueryTreeNode is constructed while parsing the sql statement. This is
the base class of all
the node created while parsing the sql statement. Probably you should
look at java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj to
see how three is generated.
You can print the parse tree by t
I am in the debugger, and
whatever I asked was in context of that (that is while debugging the
code, I am not sure where to find the access path in the QTN once the
optimize method is done with. Same for the second question).
Thanks
Aakash
On 7/12/07, *Anurag Shekhar* <[EMAIL PROTEC
SUN India is planning a contest for students to contribute to some
select open source projects. Will it be ok if apache derby is included
in it ?
The contest will be starting sometimes in aug and will last for 4-5 month.
Each contributer will receive a small award there will be few early bird
a
defend the patch in developer mailing list.
They will need help similar to any contributer needs from the community
(like getting
doubt clarified, review and commit of patch)
anurag
Rick Hillegas wrote:
Anurag shekhar wrote:
SUN India is planning a contest for students to contribute to some
enough
to continue contributions.
Regards,
-Rick
Anurag shekhar wrote:
Student will have to register them self at mention the project they
plan to participate and
also provide the id which they will be using to submit patches. They
can pickup and
existing issue or a new issue. Any committed
Reporter: Anurag Shekhar
Priority: Minor
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar reassigned DERBY-819:
Assign To: Anurag Shekhar
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: embedexception.diff
code changes to support jdbc4 SQLException and the test case for the same.
Moved creation of EmbeddedException from
java
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: stat.out
output of snv stat
> Provide JDBC4 SQLException subclasses support in Embedded dri
[
http://issues.apache.org/jira/browse/DERBY-819?page=comments#action_12363013 ]
Anurag Shekhar commented on DERBY-819:
--
SQLExceptionFactory checks for jvm version and if the jvm version is jvm16 or
above
it will instantiate JDBC40ExceptionFactory
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: (was: embedexception.diff)
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: stat.out
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: (was: stat.out)
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819.diff
changes from last patch
moved SQLException method (getSQLException) to InternalDriver
moved JDBC40ExceptionFactory metod to
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: (was: derby-819.diff)
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: (was: stat.out)
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819.diff
changes from last diff
changed Driver40.getSQLException to use theSQLState class directly
remove entry for class prefix in
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: stat.out
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: (was: derby-819.diff)
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819.diff
corrected indentation problems in Util.java and InternalDriver.java
derbyall status
5 tests failed on solaris 10 x86
derbyall
[ http://issues.apache.org/jira/browse/DERBY-839?page=all ]
Anurag Shekhar reassigned DERBY-839:
Assign To: Anurag Shekhar
> Internationalize messages CallableStatement40 to Cursor.java in
> org.apache.derby.cli
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819-onlyforreview.diff
I am attaching this patch only to get the early feed back before I go ahead and
make further changes.
In this I have
[
http://issues.apache.org/jira/browse/DERBY-940?page=comments#action_12365963 ]
Anurag Shekhar commented on DERBY-940:
--
JDBC 4.0 interface wrapper java.sql.Wrapper is meant to provide a
standurd way to access vender specific extention to jdbc calls
[
http://issues.apache.org/jira/browse/DERBY-940?page=comments#action_12365967 ]
Anurag Shekhar commented on DERBY-940:
--
>Derby doesn't implement non-standard methods on JDBC objects, that would be
>against the charter.
In that case
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819_2.diff
changes from last patch (for embedded driver)
Moved all exception methods to SQLExceptionFactory (from Util)
modified all the
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: .derby-819_2.stat
svn stat output
> Provide JDBC4 SQLException subclasses support in Embedded dri
[
http://issues.apache.org/jira/browse/DERBY-819?page=comments#action_12366069 ]
Anurag Shekhar commented on DERBY-819:
--
Description of patch
InternalDriver
added method to create ExceptionFactory. This method can be overwritten
in subclass
NetClient JDBC (40) using engine classes
Key: DERBY-983
URL: http://issues.apache.org/jira/browse/DERBY-983
Project: Derby
Type: Bug
Components: Network Client
Environment: all
Reporter: Anurag Shekhar
Assigned to
[ http://issues.apache.org/jira/browse/DERBY-983?page=all ]
Anurag Shekhar updated DERBY-983:
-
Attachment: derby-983.diff
added a new file SQLExceptionFactory
refrences of org.apache.derby.impl.jdbc.Util.notImplemented () from network
client by
jdbc4 test suite test classes are using Util.notImplemented
---
Key: DERBY-1013
URL: http://issues.apache.org/jira/browse/DERBY-1013
Project: Derby
Type: Bug
Reporter: Anurag Shekhar
jdbc4 test suite test
[ http://issues.apache.org/jira/browse/DERBY-1013?page=all ]
Anurag Shekhar reassigned DERBY-1013:
-
Assign To: Anurag Shekhar
> jdbc4 test suite test classes are using Util.notImplemen
[ http://issues.apache.org/jira/browse/DERBY-1013?page=all ]
Anurag Shekhar updated DERBY-1013:
--
Attachment: derby-1013.diff
changed the jdbc4 test classes to compare sql state and not.
> jdbc4 test suite test classes are using Util.notImplemen
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819_3.diff
Main changed I have made in this patch since the last submission
I have moved back the exception methods of Utils
[
http://issues.apache.org/jira/browse/DERBY-819?page=comments#action_12367604 ]
Anurag Shekhar commented on DERBY-819:
--
There were some ? chars in SystemProcedures.java )all of them in comments) I
checked my files It apears to me that some how there
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819_4.diff
change from last patch
added coment in SQLExceptionFactory40 explaining that application relying
on EmbeddedSQLException
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: (was: derby-819_4.diff)
> Provide JDBC4 SQLException subclasses support in Embedded dri
[ http://issues.apache.org/jira/browse/DERBY-819?page=all ]
Anurag Shekhar updated DERBY-819:
-
Attachment: derby-819_4.diff
created a new test case jdbc4_embedded as TestJDBC40Exception is ment only for
embedded mode
and jdbc4 test suite uses net
[ http://issues.apache.org/jira/browse/DERBY-942?page=all ]
Anurag Shekhar updated DERBY-942:
-
Attachment: derby-942.diff
This patch is meant only for review. Because of bug in current version of
jdk1.6 (mustang) ResultSet.getType after closing
: Improvement
Environment: all
Reporter: Anurag Shekhar
A new method getQueryObjectGenerator is added in CommonDataSource. This effects
all the DataSource (XADataSource, PooledDataSource and DataSource). Because of
this new method we will need to have seperate classes for all the DataSouce
[ http://issues.apache.org/jira/browse/DERBY-1051?page=all ]
Anurag Shekhar reassigned DERBY-1051:
-
Assign To: Anurag Shekhar
> A new method in CommonDataSource added which is not present in jdbc4 stub
> c
1 - 100 of 449 matches
Mail list logo
