yonestar wrote:
Hi,
I have a large table (1 million rows). I want to write its contents to a
file, in a specified csv format.
Have you tried to use Derby's built-in stored procedure for export,
SYSCS_UTIL.SYSCS_EXPORT_TABLE() ?
If i try to get all the rows at once, i run out of heap
Jørgen Løland wrote:
In the current proof of concept replication code, we boot the slave
database by calling
Database db =
(Database)Monitor.findService(Property.DATABASE_MODULE, dbname);
This requires org.apache.derby.iapi.db.Database to be imported. With the
head of trunk, this import
Oystein Grovlen - Sun Norway wrote:
I get this error without any changes to NetworkServerControlImpl. (My
only changes are some local changes in LogToFile). I think the problem
is that VTI demo does not implement Blob methods that are new to JDBC 4.
I guess either the build system should
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*tinderbox_trunk16* 584717/2007-10-15 11:42:16 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0288288 088.41% derbyall
Kathey Marsden wrote:
I've been thinking quite a bit about the bug backlog and was wondering
what it might take to get the community motivated to fix bugs. I decided
that what might really help is a maintenance release. We already have
some valuable fixes in 10.3 which users have asked for.
+1
--
Øystein
Rick Hillegas 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 contributions range
Myrna van Lunteren wrote:
I will close this vote on July 23, 16.00 PDT
If positive, we can have a release by July 24 5 pm (PDT) (I haven't
done this bit yet so I'm reserving some more time than I hope to
need).
To vote:
[+1] Make the release candidate (10.3.1.2 - (SVN 556213)) the
Myrna van Lunteren wrote:
I took advantage of the need for some time for the blockers and
revised the Release Notes manually...
1. I went through and wherever it seemed an issue would have existed
beforeI left it in the CHANGES section; if it looked like it was new
with 10.3 and fixed in 10.3 I
For ad hoc testing, you could perhaps try to create a system/wombat
database manually with 10.2, and then run the JUnit tests against that
database with the allowPreReleaseUpgrade flag. Not sure if it works, but
it's worth a try.
This was a very excellent idea, Knut Anders. It seems to work
Myrna van Lunteren wrote:
On 7/11/07, Øystein Grøvlen (JIRA) [EMAIL PROTECTED] wrote:
I think this bug requires a new release candidate. Blob/Clob will not
work correctly in soft upgrade mode if this is not corrected. I
thought I had tested this earlier, but I must have done a mix-up of
Bryan Pendleton wrote:
1) try to code access privileges in the routines themselves, that is
separate from java security manager. Basically
disallow access to derby files by adding code logic to determine if
the files being read/written are derby files.
Instead of trying to write this
Myrna van Lunteren wrote:
One of the hardest and most time-consuming things in preparing the
release was creating the Release Notes.
We have the release notes generator...But it presumes xml reports to
have been magically created, and it does not have a mechanism to
identify the new
Kathey Marsden wrote:
Myrna van Lunteren wrote:
On 7/9/07, Stanley Bradbury [EMAIL PROTECTED] wrote:
Hi Myrna -
Thanks for the through release report. I took a look at the critical
bug list and am concerned about the regression that causes locking
problems:
DERBY-2892
Thanks for all your work on making the 10.3 release, Myrna. I have
downloaded the release candidate and plan to do some ad-hoc testing of it.
I looked at the release note and I found the CHANGES section a bit
confusing. It lists a lot of issues that are not relevant to users
(e.g, code
Daniel John Debrunner wrote:
This is an open source release, the release note applies just as much to
the source code as the libraries. Probably even the test issues should
have been listed.
It might be better to split the changes section into two (or more)
sections, e.g. changes in the user
How can I add to the list of new features in the release note? Can I
just edit the DerbyTenThreeRelease wiki, or should I edit the release
note directly? The addition of the Blob/Clob API mehtods seems to have
fallen out. (However, I am pretty certain I added them to the wiki a
long time
Anurag Shekhar (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Shekhar updated DERBY-1341:
--
Attachment: releaseNotes-v2.html
thanks Øystein for the review.
Myrna van Lunteren wrote:
1. code complete 6/1
For those of you who plan to have functionality fixed/completed in
10.3, please analyze your progress, and let me know if you think you
will not make that date.
There are a few issues listed on the DerbyTenThreeRelease page that I
Kristian Waagan wrote:
However, using UTF-16 imposes space overhead when operating on Clobs
with US-ASCII characters, in fact the overhead is 100% (each character
represented by two bytes instead of one). For some other languages
(and/or character sets), using UTF-16 reduces the space
Mike Matrigali wrote:
What is the expected usage pattern for an update on a clob that uses
these temporary clobs? What is the usual input format, what is the
usual output format? Do you expect more than one update usually? Does
an update have to rewrite the end of the file on and shrink or
Knut Anders Hatlen wrote:
Kristian Waagan (JIRA) [EMAIL PROTECTED] writes:
Committed 'blobframework_v2.diff' to trunk with revision 529185.
Very nicely commented patch Øystein!
OK, so I'm more than three weeks late to review the patch... :)
Anyway, I came across
Knut Anders Hatlen (JIRA) wrote:
But the behaviour that needs to be exhibited for
InputStream/OutputStream
methods after close was not mentioned.
I found this the javadoc for OutputStream.write(int):
IOException - if an I/O error occurs. In particular, an IOException
may be thrown if
Daniel John Debrunner wrote:
I think testNetworkServerSecurityMechanism is being worked on but is
anyone looking at reducing the time for testPositionAgressive?
I have created DERBY-2596 for the testPositionAgressive problem.
--
Øystein
Daniel John Debrunner wrote:
Oystein Grovlen - Sun Norway wrote:
...
Some observations I have made:
- In embedded, objects for short LOB values are valid after
transaction commit, objects for long values are not. The same
holds after the connection is closed.
seems
Bryan Pendleton (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488531 ]
Bryan Pendleton commented on DERBY-2526:
The UpdateCursorTest failure appears
As part of the work on using locators for Blob/Clob, we will need to
be able to determine when to garbage collect information about locators.
The JDBC spec says the following about lifetime of Blobs [JDBC 4 spec,
section 16.3.1]:
For locator based implementations, Blob, Clob and NClob
Øystein Grøvlen wrote:
I have looked around in the client trying to find whether there are
other mechanism with similar needs, but I have not found anything yet.
Can anyone point me to existing code where the client execute
sql-statements as a side effect of user operations. (Maybe there are
I have an hard limit of 255 storage entities, files and directories. Is
it possible to make derby work for a medium size database (10-20 tables,
10-100k records) with this limit?
An empty database with just system tables etc has less than 70
files/directories. Then you will use a few log
Daniel John Debrunner wrote:
I was wondering if a callback system might be better. The LCC would
provide an api where objects could be added and have methods called on
rollback, commit or statement rollback. This then would make the
commit/rollback methods very clean, and ensure that the
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.
+1
--
Øystein
Manjula Kutty (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manjula Kutty closed DERBY-2395.
Resolution: Fixed
There is a similar test called
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:
--
Why use the system
Saurabh Vyas (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463865 ]
Saurabh Vyas commented on DERBY-1963:
-
I tried reproducing this, but while using the
Rick Hillegas wrote:
2) What behavior would we like to see in 10.3 when we control engine
shutdown with Java Security?
I think we need to prevent unauthorized users from bringing down the
network server. I wonder if there is much difference between the power
to shutdown the engine and the
Daniel John Debrunner wrote:
Julius Stroffek wrote:
I have only two solutions to this:
1.) Change the visibility of required classes to public.
2.) Maintain the parallel package tree (suggested by Krisitian) with
implementation of tests of private classes. The tests will be in a
same package
Ole Solberg wrote:
I rebuilt from the same source, but now with 'debug=false' and ran
derbyall on the same host: predicatePushdown did NOT fail.
So this seems to be the same instability as in e.g. the Wisconsin test,
and triggered by larger/slower(?) code causing an unexpected query plan
to be
Bryan Pendleton wrote:
The patch also contains a change to AllPackages.java in order
to run the derbynet suite only once. (I found that an entry
for this suite had been added twice.)
Is it possible that this was present twice because one occurrence
was for the Derby client driver and
Daniel John Debrunner wrote:
So maybe if Derby is booted as a standalone server with no security
manager involved, it should install one with a default security
policy. Thus allowing Derby to use Java security manager to manage
system privileges but not requiring everyone to become familiar
Rick Hillegas wrote:
It seems to me a sysadmin needs our system privileges because she wants
to prevent malicious shutdown (shutdownEngine privilege) and resource
hogging (createDatabase privilege). I suspect that she also wants to
control malicious shutdown via unauthorized calls to
Mike Matrigali (JIRA) wrote:
The case I am trying to work out in my mind is the space reclamation thread. It gets latches on pages and
loops through rows requesting zero duration locks to see if it can purge a row from a page. In the first case
the row we are requesting a lock on will never
Dag H. Wanvik (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458129 ]
Dag H. Wanvik commented on DERBY-2109:
--
Øystein:
I miss a rationale for how you ended up with three
database-specific features.
Mike Matrigali wrote:
I assume changes to remove latching out of
lock manage will break existing in progress work to do in memory store -
but I don't know for sure.
I would not think so since AFAIK that work is just replacing the current
io system with memory. Hence, it should still operate
Manish Khettry wrote:
Hmm strange. I am not sure why this
select avg(i) from t group by sin(i)
works but not this,
select avg(i), sin(i) from test group by sin(i);
I think its a bug-- both should be disallowed.
Why should they be disallowed? I agree that in most cases grouping by
Yip Ng wrote:
On 11/14/06, *Oystein Grovlen - Sun Norway* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Just some late follow-up here. As far as I can tell, it is not
strictly
correct to say that non-deterministic functions does not work
with group
by expressions. What
Yip Ng wrote:
For SIN, COS, TAN functions, they are also considered deterministics.
However, they do not work currently in Derby with group by expression as
they are mapped to JavaToSQLValueNode and such nodes always return
false in isEquivalent() method, so I think this is an
Jean T. Anderson wrote:
I propose that we add Laura Stewart as a committer for Derby.
+1
--
Øystein
TomohitoNakayama wrote:
Hello.
Thank you for your kindness :)
What is needed is calling method which was introduced in JDBC 4.0
from NetworkServer to utilize JDBC 4.0 feature in Engine.
Concretely,the method is PreparedStatement#setBinaryStream(int,
java.io.InputStream).
Rick Hillegas wrote:
Please vote on whether we should make Kristian Waagan a Derby committer.
+1
--
Øystein
Andrew McIntyre wrote:
...
But, that decision in the code means if you 'set schema sys' and then
'show tables' you get no output. That's bad behavior, in my opinion.
I agree.
...
I've attached a patch which changes the behavior to adjust the
behavior of show tables to what you describe,
Daniel John Debrunner wrote:
Just to note, .sql tests can be converted with very little effort by
using the ScriptTestCase utility class, see LangScripts for an example
of its use in language tests.
One of my motivations for converting to a new test framework (Junit) is
to get rid of most
I find it strange that while SHOW INDEXES, SHOW PROCEDURES, and
SHOW SYNONYMS by default list all corresponding objects in the
database, SHOW TABLES and SHOW VIEWS by default only list the
corresponding objects in the current schema. Would it not be better
if all commands behaved the same way?
Daniel John Debrunner wrote:
Please vote +1 if you agree Fernanda should be a committer.
+1
--
Øystein
A B (JIRA) wrote:
Interesting observation about the disk cache--thanks for bringing that up. Is
it feasible to turn disk cache on for one of the machines that's failing and
run the tests for a couple of days to see if that makes a difference? Thanks
Øystein...
I can turn the disk cache
Daniel John Debrunner wrote:
I'm preseting at ApacheCon US 2006 the topic What's new in Derby 10.2,
and there's a lot of stuff, more than I thought, so thanks everyone.
I'm working off the (different!) lists here:
http://wiki.apache.org/db-derby/TenTwoSnapshot
Bryan Pendleton wrote:
Oystein Grovlen - Sun Norway wrote:
Oh, I did not notice this. I tried to run batchUpdate with
DerbyNetClient, but this still fails. I guess that means that beetle
5561 is still an issue
Perhaps this is worthy of a JIRA issue of its own, something along the
lines
Bryan Pendleton wrote:
Oystein Grovlen - Sun Norway wrote:
Oh, I did not notice this. I tried to run batchUpdate with
DerbyNetClient, but this still fails. I guess that means that beetle
5561 is still an issue
Perhaps this is worthy of a JIRA issue of its own, something along the
lines
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*TinderBox_Derby* 433085/2006-08-21 01:22:24 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
2672670 2 154.08% SunOS-5.10_i86pc-i386
Gokul Soundararajan wrote:
I have placed the code and report on my website at:
Report
http://www.eecg.toronto.edu/~gokul/derby/derby-report-aug-19-2006.pdf
Code
http://www.eecg.toronto.edu/~gokul/derby/code/aug-19-2006/
Gokul,
Thank you very much for your work so far. It would be nice if
Yip Ng wrote:
From what the problem description states, it seems so. The symptoms of
this jira
matches those of DERBY-1652. I'll leave it up to the reporter to decide
if it is a
duplicate.
As far as I understand, DERBY-1652 makes this fail also when only a
single trigger is defined. So
Rick Hillegas wrote:
Clarity is the key goal of Derby's coding standards. The coding
guidelines at
http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html are a style
primer, not a law book. Mine this document for good examples but use
your common sense. Feel free to disregard any
Mike Matrigali (JIRA) wrote:
I ran this change 20 times and it worked on my laptop, it would always fail
a few times out of 20 before the fix. I am not sure why this fix works as
the test seems to already create indexes after tables so statistics should
already be up to date.
While it is
Stan Bradbury (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1431?page=comments#action_12417004 ]
Stan Bradbury commented on DERBY-1431:
--
I like to plan for success. To me that means, in this case, many more demo
programs, databases,
Merlin Beedell at Demon wrote:
I hope that this is a common enough request that some results and
comments already exist. Just point me in the right direction!
I would like to know how Derby performs (inserts and search) where the
record count goes from 1 to 1,000 million or greater,
Anders Morken (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12413541 ]
Anders Morken commented on DERBY-801:
-
I've found a benchmark to test this patch with, and quite frankly I'm not seeing any difference in
Anders Morken wrote:
I've played around a bit with a different approach - using the
FileChannel class from Java 1.4's new IO API. I've written a class
RAFContainer4 which extends RAFContainer and overrides the readPage and
writePage methods of that class to use read/write(ByteBuffer buf, long
Ashwin Jayaprakash wrote:
Hello,
I'm posting several questions about Perf tuning. I'd be grateful if
people can provide me with answers.
I'm using Derby as an Embedded Database for a prototype application,
where Derby is used to run queries on a small set of Rows, very
frequently. Rows are
Mike Matrigali wrote:
One suggestion was using an open source product which captured the info
at the jdbc level. Also others have used triggers to provide the
necessary information.
One problem with statement-based replication (e.g., at JDBC level) is
that statements are not idempotent.
Anders Morken wrote:
I've written a project proposal for Google's Summer of Code program at
http://wiki.apache.org/general/AndersMorken/SoCProp - I'd be grateful
for any suggestions for improvements or corrections you might have. This
request especially goes out to Øystein Grøvlen, who has
Huinan wrote:
Hi,
I am tring to build an application that captures changes in Derby
database.For example, as a new query inserts data to some table comes, I
want to be able to get that change without using trigger for scalability
and loose coupling reasons.
The solution I'm considering is
As far as I understand, the story is different for the embedded and the
client here. According to DERBY-572, client supports
Blob.setBinaryStream(), embedded does not.
--
Øystein
Rick Hillegas (JIRA) wrote:
Finish JDBC3 Blob implementation
Key:
It is not a good idea to always add new items at the end of a list.
That increases the risk of conflicts between check-ins. I think for
most of the test suites one has tried to maintain an alphabetical ordering.
--
Øystein
Kristian Waagan wrote:
Hello,
ParameterMetaDataWrapperTest.junit is
David W. Van Couvering wrote:
Hi, all. Students can make proposals from May 1 to May 8. The ASF page
http://wiki.apache.org/general/SummerOfCode2006 is the official ideas
page for the ASF that students will be looking at, and probably already
are.
I just updated
Bryan Pendleton wrote:
1) There are two basic configurations of interest here:
a) In the simple Network Server case, the Network Server process
is providing access to the database(s) over DRDA
b) In the dual-access configuration, an application which has
established embedded
David W. Van Couvering wrote:
What we actually submit to the ASF Summer of Code Wiki, however, needs
to be a project that makes sense for Summer of Code and needs to have a
committer who has volunteered to mentor.
Why does mentors have to be committers? Is that a Google or Apache
Dag H. Wanvik (JIRA) wrote:
Minor nit-picks:
- EmbedDatabaseMetaData.java
* Code readability:
if ((removeSYSIBMonly isSYSIBM) || !removeSYSIBMonly) {
do something
}
might be more readable as:
if (removeSYSIBMonly !isSYSIBM) {
// do nothing
} else {
do
Sunitha Kambhampati (JIRA) wrote:
Ran derbynetclientmats with patch on linux/ibm142. Apart from the known
failures, the test lang/ConcurrentImplicitCreateSchema failed with the timeout
exception (Note - this test was fixed for the timeout issue on trunk). This
failure is not related to this
TomohitoNakayama wrote:
Hello.
Yes for blob.
What makes blob different from clob? I would have guessed that the
implementation of clobs and blobs should be very similar.
--
Øystein
Mike Matrigali wrote:
I am most concerned about 7 to 8, that should reduce space assuming
the 171 rows don't all fit on a page.
Does this mean that it is only space in completely empty pages that will
be reused when defragmenting?
one question, what sizes of rows are you using (basically
Daniel John Debrunner wrote:
Remember this is open-source, there are no customers or important
customers, only users and developers.
If a user doesn't like the solution they have at least two options:
- get involved in the Derby developer community
- patch the source
I prefer the
David W. Van Couvering wrote:
Please see http://wiki.apache.org/db-derby/ForwardCompatibility, and
modify or comment as you see fit. It is not necessarily my itch to be
the one responsible for maintaining this interface table; I hope that's
something that can be shared across a number of us.
David W. Van Couvering wrote:
I am also realizing that we as a community need to decide if we want
to ensure that the network client and the engine should always have
the same SQL States for the same exceptions. It's laudable, and if we
catch differences I think we should fix them, but I am
Raymond Raymond wrote:
I ran a variant of the TPC-B benchmark with a large database (20 GB)
and a large page cache (1 GB). I do not think you need TPC-B
transactions to see this, but I think you need update-intensive
transactions that frequently needs to load pages from disk. For
example,
Francois Orsini wrote:
Grant or Revoke statement would have to succeed to enable sqlStandard
authorization mode automatically, with someone having enough privilege
to issue a successful Grant/Revoke operation in the first place - at
the same time, implictly and silently setting the
Mike Matrigali wrote:
The way I look at it, derby has a very nice default. We call it soft
upgrade, but in my mind it really is no upgrade. We guarantee that
if you do nothing to your existing app, then you can run it and the
database against your current version of the derby software and all
Daniel John Debrunner wrote:
Oystein Grovlen - Sun Norway wrote:
I was thinking of exisiting applications running against existing
databases vs new applications on a new database; not both existing and
new application against the same database. In other words, would it be
possible to turn
I agree that soft upgrade has a value, but I think you give soft upgrade
credit for things that are actual not provided by soft upgrade. More
comments below.
Kathey Marsden wrote:
Rick Hillegas wrote:
4) What is the customer problem solved by Soft Upgrade?
Soft upgrade solves many
Olav Sandstaa (JIRA) wrote:
Dan has suggested that checking for isClosed could be sufficient in the
embedded version. It would be good to hear if other have opinions about this.
If I do not get other suggestions I will probably propose that the next patch
(checking only for isClosed) being
Kathey Marsden wrote:
There is some info here:
http://db.apache.org/derby/papers/versionupgrade.html#Version+Upgrade+Mechanism
I think we could safely add metadata to the list of items requiring
upgrade thought.
This provides useful on how it is supposed to work, but is there any
guidelines
Rick Hillegas wrote:
3) It appears that we expect to be able to run down-rev clients against
up-rev servers running against down-rev data. For the most advanced
server rev, the clients can range over all previous versions and so can
the data. If there are N previous versions, Soft Upgrade
Kathey Marsden wrote:
There is some info here:
http://db.apache.org/derby/papers/versionupgrade.html#Version+Upgrade+Mechanism
I did not understand the purpose of item 7 in the list that describes
the behavior when the engine version is different from the on-disk
version. It says:
7.
Kathey Marsden wrote:
Regardless of whether we provide a mechanism allow soft upgrade, I
think that databases that have been modified by alpha software should
not be accessible by a released Derby version and thus be allowed carry
any undetected corruption with them into a supported
Satheesh Bandaram wrote:
Oystein Grovlen - Sun Norway wrote:
Satheesh Bandaram wrote:
At some time in the future when GRANT/REVOKE support is more complete,
would it be possible to have some way to turn on SQL authorization
automatically when GRANT/REVOKE is used for the first time? I think
Instead of using export import of data to a new engine, users can
restore from the backup on the same version of the engine at diffent
location and then do the testing by setting
derby.database.allowPreReleaseUpgrade=true
I tried to find a description of this property, but was not able
Satheesh Bandaram wrote:
No... Default authorization model in Derby 10.2 is still legacy mode..
So if you create a database without setting sqlAuthorization property,
you shouldn't be able to do GRANT/REVOKE. Only if you have the property
set to true, SQL authorization would be enforced. This
Andreas Korneliussen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1067?page=all ]
Andreas Korneliussen updated DERBY-1067:
Attachment: DERBY-1067v4.diff
storeunit_report.txt
Attaching patch to fix some JavaDoc
Andreas Korneliussen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12370325 ]
Andreas Korneliussen commented on DERBY-690:
11.2 positionAtRowLocation()
a) Why can not clients use the existing
Sunitha Kambhampati wrote:
Hi All,
I ran javadoc on the trunk and I see the following 3 javadoc warnings.
Maybe we should require patch submitters to run javadoc in addition to
derbyall before submitting a patch.
--
Øystein Grøvlen, Senior Staff Engineer
Sun Microsystems, Database
Daniel John Debrunner wrote:
CREATE SCHEMA
- only create schema matching user's name
- good for now, forwards compatible with the
future where permission to create any schema
could be granted explicitly.
Does this mean that we will only allow one schema per user? That seems
V.Narayanan (JIRA) wrote:
-- In this specific case I did'nt put in method level javadoc comments for the
Impl classes because they inherit the javadoc comments of the interface. If you
still feel that they need class level comments I will add these too.
There is a lot of examples in Derby
99 matches
Mail list logo
