Hi Mag,
Thanks for bringing up this issue. It certainly deserves an enhancement
request. I'll log one later on today.
Technically, you can build your own poor-man's solution to this problem
today:
1) You can build your own inverted index (as a full-fledged table) on
the text column you
Hi Sube,
Is it possible that you have brought up two copies of the Network
Server, listening on different ports? Connecting to the same database
through two servers would cause the error you're seeing. Granular Derby
locks (among other objects) aren't shared across servers. When the first
Hi Bryan,
Nice to see you on the list. It may be that the database which would
remain nameless is Oracle. Oracle treats 0-length strings as null. Note
that Oracle documentation confesses that this is a bad idea and darkly
hints that future versions of Oracle may conform to the standard
Hi Bryan,
Derby supports adding but not dropping columns. An enhancement request
(396) has been filed on this issue.
Regards,
-Rick
Bryan Pendleton wrote:
I tried
alter table my_table drop column my_column;
and I got:
ERROR 42X01: Syntax error: Encountered drop at line 4, column 27.
Derby does have a RENAME TABLE command.
Cheers,
-Rick
Michael J. Segel wrote:
On Thursday 08 September 2005 20:09, [EMAIL PROTECTED] wrote:
Hi Susan,
Is there any other way we can drop columns
which are not objects you mentioned ?
or impossible ?
thanks,
Wolfgang
You could always
Hi Tony,
The syntax is, unfortunately, rigid. What do you need to do? Do you want
to avoid declaring each overload because your overloads are changing
rapidly? Are you using Java 1.5 varargs?
Thanks,
-Rick
Tony Seebregts wrote:
Hi,
Is there a way to specify variable length parameter
Hi Mag,
This issue (bug 472) is certainly on my wishlist but since it's a modest
sized feature, it won't get into the October release. We need someone to
work on this feature and no-one has been donated to this effort yet.
You're welcome to help out!
Cheers,
-Rick
Mag Gam wrote:
I would
plausibly learn.
o The current Derby optimizer is capable of considering only a very
limited subset of the useful plans.
Cheers,
-Rick
[EMAIL PROTECTED] wrote:
Rick Hillegas wrote:
It might help to add another column to the index so that it covers
both the restriction and the ordering
Hi Michael,
I'm not sure I understand the problem you're wrestling with. Forgive me
if I have garbled your message. It sounds as though you want to be able
to create an empty database from a template database. This is pretty
easy to do with Derby:
1) Nest another jar file inside your
Thanks for the pointer to this presentation, Oyvind. It's a pretty
startling observation though I'm not sure how to use it. I'd be
interested in hearing your thoughts about this some time.
Cheers,
-Rick
That reminds me of a very entertaining presentation which was held at
VLDB this year:
Hi Tony,
You could try using a temporary table to hold your parameter values. By
changing the contents of the temporary table you might achieve what you
want. Something like the following:
declare global temporary table session.ztemp
( param int )
not logged;
select *
from names
where id
Hi Nicolas,
I don't know if anyone got back to you on this one. You can always
create your own function to do this. The java code would look something
like this:
publicstaticStringdayOfWeek( java.sql.Date date )
throws Exception
{
GregorianCalendarcalendar
Hi Chas,
Derby doesn't support this feature today. This has been logged as
enhancement request 396.
Regards,
-Rick
Chas douglass wrote:
Does Derby support a rename column version of ALTER? Random experimentation has
failed to reveal it to me.
Chas Douglass
I have moved the discussion about Full Text Indexing onto a wiki page:
http://wiki.apache.org/db-derby/LuceneIntegration
Right now this page lists some features and use cases which we might
want this integration to support. Please feel free to add your own
feature requests and use cases.
Hi Frederic,
This looks like a bug. I have logged bug 649 to track this issue. Thanks
for the detailed test case.
Regards,
-Rick
Frederic MOREAU wrote:
Hello,
The optimizer does not take my indexes into account when I do a select
on a 'UNION ALL' type of view ; therefore, table scans
Hi Dan,
I believe that the Sybase behavior is correct. I have logged bug 653 to
track this issue.
Regards,
-Rick
Dan Meany wrote:
I noticed that in Derby a unique constraint on two
columns A and B, with B nullable, will prevent
inserting two identical records that contain NULL in
B.
This
Thanks, Michael. You are correct, Derby, like DB2, finesses this issue
by not allowing nullable columns in unique constraints. I have closed
this bug.
Cheers,
-Rick
Michael J. Segel wrote:
On Wednesday 26 October 2005 19:22, Rick Hillegas wrote:
Sorry to top post...
Sigh.
Seems that some
Recently, some provocative postings have appeared on this list. Probably
the poster's colorful language was meant to sound playful and bantering.
Unfortunately, it has offended some people. This would be a good time to
remind everyone that the Derby community prides itself on being open,
Hi Chas,
Derby raises an exception with the text Invalid transaction state.
However, that message has a different sql state (x0x03) than the one
you're seeing. Here's the blurb from the Derby code describing what
makes Derby raise this exception:
// find if there are any held cursors
Thanks, Øyvind.
Cheers,
-Rick
[EMAIL PROTECTED] wrote:
Rick Hillegas wrote:
Hi Øyvind and Naka,
I think you both may be working on fixing the same problem: the
broken regression tests. The tests were broken by the fix to bug 330
and now Naka has filed bug 663 against the test problems
Hi Nicolas,
In old releases of Cloudscape, customers were able to create their own
aggregates. This functionality was removed from Derby probably because
the syntax was considered non-standard. Most of the machinery for this
feature is still in the code and it should be easy to re-enable once
Hi Edson,
Enhancement request 396 tracks this issue and Scott MacDonald is working
on it. For current capabilities, see the ALTER TABLE section of the
Reference Manual. In a nutshell, you can't drop a column.
Cheers,
-Rick
[EMAIL PROTECTED] wrote:
I have found no way to drop a column from
Hi Erik,
I am not sure I understand your query. However, it looks to me as though
it is trying to inner join DATACOLLECTION_ELEMENT to the previous left
join result. The compiler is objecting that THIS.ID is not a column in
either DATACOLLECTION_ELEMENT or the previous left join. THIS is the
Hi Arieh,
I haven't run any experiments but I would expect that you would have to
be careful about how you commit this work. If one thread commits the
connection while another thread is in the middle of a statement, someone
is likely to be disappointed.
You will likely have deadlock issues
Hi Lars,
count(*) iterates through the rows. I don't think it's any faster than
count( colName ).
-Rick
Lars Clausen wrote:
On Thu, 2005-11-10 at 04:41, Jeffrey Lichtman wrote:
1) A null column is excluded from a COUNT( colName ) aggregate. This
is described in the section 10.9 under
I'd like to factor out the DRDA constants into a single class which can
be shared by the client and server. Where should I put a file like this?
Perhaps
java/drda/org/apache/derby/iapi/drda
Thanks for your advice,
-Rick
Hi Michael,
You could streamline your recursive walk by using a temporary table and
a database procedure. The temporary table would hold the ids you
recursively harvest. It would be populated by your database procedure,
which would walk up the levels of your hierarchy. When the procedure
+1
Bernt M. Johnsen wrote:
David W. Van Couvering wrote (2005-12-06 11:11:12):
Hi, all. Many of us will be at ApacheCon in San Diego next week. There
is a Derby BoF from 9:30 - 10:30 on Tuesday night. I was thinking that
perhaps those of us who are there could
like HSQL?
I do not want persistence, just SQL operations on a few thousand rows
in-memory (I know this should've been posted as a separate question,
well..)
It looks like Dag has sent you advice on this topic.
Thanks,
Ashwin.
On Tue, 03 Jan 2006 Rick Hillegas wrote :
Hi Ashwin,
I
We're setting up a lunch for bay area folks who use or work on Derby.
We're planning on Wednesday February 1 in San Francisco--details to
follow later. Let me know if you're interested in attending.
Regards,
-Rick
I am tracking down a problem with autoloading jdbc drivers when running
from jar files under the Derby test harness on jdk1.6. Capsule summary:
SUCCESS-1 The drivers correctly autoload (from the information in the
jar file) when I run my test program standalone (without a SecurityManager)
Soft Upgrade is a feature which I think was introduced after I left
Cloudscape. Please bear with me as I try to understand how Soft and Hard
Upgrade interact.
In the old days, when there was only Hard Upgrade, Upgrade satisfied the
following contract:
o Transitive - You could upgrade data
A while ago, I volunteered to manage a Derby release which will include
a new feature that is important to me: an implementation of JDBC4. Based
on the JDBC4 schedule then, I had hoped to post that release in June.
However, because the JDBC4 schedule moved back, I must post my release
later,
Although this won't help anyone solve the immediate problem immediately,
this issue would be addressed by DERBY-455 (expression indexes).
Regards,
-Rick
Craig L Russell wrote:
If you are concerned about performance, please note that there is a
huge difference between these two statements:
Dear Derby users,
Please read this message if you work on an application server or in an
application layer which cares about distributed transactions and/or
pooled connections.
Right now the inheritance graph for Derby's DataSources does not mirror
the corresponding graph of interfaces in
Thanks for forwarding this, Kathey.
Regards,
-Rick
Kathey Marsden wrote:
Rick Hillegas wrote:
Dear Derby users,
0Please read this message if you work on an application server or in
an application layer which cares about distributed transactions
and/or pooled connections.
Right now
Hello users and developers,
We have posted a new snapshot of the mainline, which we expect will
evolve into the 10.2 release this fall. You may find the snapshot at
http://db.apache.org/derby/derby_downloads.html#Snapshot+Jars. We would
be grateful if you would test-drive this snapshot and
, 2005 / SVN 330608)
but later on in the same page it appears that 10.1.2.2 and 10.1.2.3
were released already.
Thanks,
Craig
On May 26, 2006, at 2:50 PM, Rick Hillegas wrote:
Hello users and developers,
We have posted a new snapshot of the mainline, which we expect will
evolve
.
With the Derby jar files posted in this way, we could contribute more
easily to the testing effort.
Thanks,
Craig
On May 26, 2006, at 2:50 PM, Rick Hillegas wrote:
Hello users and developers,
We have posted a new snapshot of the mainline, which we expect will
evolve into the 10.2 release
I have replaced this snapshot with a new cut: 10.2.0.2. The test
machinery in the previous snapshot was broken. That machinery is fixed
now and the new snapshot passes the Derby regression tests.
Regards,
-Rick
Rick Hillegas wrote:
Hello users and developers,
We have posted a new snapshot
I have updated the 10.2 snapshot with a new version, 10.2.0.3, available
at http://db.apache.org/derby/derby_downloads.html#Snapshot+Jars. This
version fixes a couple issues:
1) Messages should print out in the correct language now because
localized message files are wired into the classpath
I'm going to make some copy-editting fixes to the user guides. While I'm
in there, I'd like to update the copyright notices. I'm proposing to
change the following line:
Copyright 1997, 2005 The Apache Software Foundation or its licensors,
as applicable.
to
Copyright 1997, 2006 The Apache
Thanks, Jean. This sounds like it's still in flux and will require some
sort of rototill of all the documentation source files. I'll hold off on
changing the copyright until this settles down.
Regards,
-Rick
Jean T. Anderson wrote:
Rick Hillegas wrote:
I'm going to make some copy
This feature (DERBY-396) is currently unassigned. Someone could still
make good progress on this feature in the time remaining for the 10.2
release, and the community would be delighted to give advice. :)
Regards,
-Rick
Regards,
-Rick
Edson Carlos Ericksson Richter wrote:
There is any news
Hi Edson,
By using the RENAME TABLE command, you can eliminate one of the
data-copies mentioned in your workaround.
Regards,
-Rick
Edson Carlos Ericksson Richter wrote:
Unfortunately, for developers, TBDITW don't allow change column names,
datatypes, nullability, etc...
At least, no
Dear Derby users,
I would like to understand if anyone thinks that they might be affected
by the following issue. This issue affects customers who do the following:
o Run an embedded Derby application which generates its own Derby
properties on the fly.
o In the same VM, run other JDBC
and JBoss perspectives.
Thanks
Charlie Kelly
P.S. What is a Heisenbug?
Sorry for the jargon. It's a term which Jim Gray coined for bugs which
arise from non-deterministic behavior and which can disappear when you
instrument the application to look for them.
Regards,
-Rick
Rick
Last week, Sun Microsystems announced that it will bundle Derby with the
next major release of the reference jdk, Java SE 6, also known as
Mustang or jdk1.6. If you download the latest Mustang build, you will
see that it contains our Derby 10.2.0.3 snapshot in the db directory
parallel to lib
Hi Andrew,
Like you I'm happy that Geir Magnusson is working the JCP issues and I'm
optimistic that the time line, which had been twisted into a pretzel,
can be straightened out. I'm not ready to propose an alternative--but I
expect to know more soon. Something along the lines of your
Hi Kathey,
Right now, I'm planning to back out BOOLEAN before the branch.
Regards,
-Rick
Kathey Marsden wrote:
Rick Hillegas wrote:
Hi Andrew,
Like you I'm happy that Geir Magnusson is working the JCP issues and
I'm optimistic that the time line, which had been twisted into a
pretzel
before re-enabling BOOLEAN.
My vote would be for (2c) but I don't sense enough enthusiasm for
BOOLEAN to justify a major release in the near term.
Regards,
-Rick
Kristian Waagan wrote:
Rick Hillegas wrote:
Hi Kathey,
Right now, I'm planning to back out BOOLEAN before the branch.
Hi Rick
I have generated a new 10.2 snapshot, which rolls up improvements that
accumulated over the last month. Please test-drive it. You can download
the snapshot from
http://db.apache.org/derby/derby_downloads.html#Snapshot+Jars. For more
information, see the wiki page describing the snapshot:
Hi Jitendra,
Jitendra Kharche wrote:
Thanks Kristian.
I checked. The column size is smaller than the data being inserted.
I have two questions
1. Does Derby support java data types like cloudscape?
I think you may be asking whether Derby, like Cloudscape, supports
abstract data types,
Hi Joel,
There is a lot of interest in enabling the BOOLEAN datatype.
Unfortunately, our first attempt at this foundered on network protocol
and release-compatibility issues. At this time, we don't understand how
to enable this datatype without issuing a major release of Derby
(release 11).
As part of building the beta, I will need the j2me pieces needed to
trigger the building of the optional jsr169 support. Could someone email
me the relevant classes.zip and jdbc.jar referred to by BUILDING.txt?
Getting my hands on these files is proving to be a chore. I have
downloaded what I
Please test-drive the 10.2.1.0 beta candidate, available at
http://people.apache.org/~rhillegas/10.2.1.0-beta/. I have updated the
10.2 release page to direct you to the beta candidate:
http://wiki.apache.org/db-derby/TenTwoRelease. I have also updated the
snapshot description page with more
Hi Robert,
The Derby Developer's Guide explains how to load the database with jar
files of user-written functions and procedures. Please see the following
section of that guide:
Deploying Derby Applications - Loading classes from a database
Hope this helps,
-Rick
Robert Enyedi wrote:
A new Derby beta candidate, 10.2.1.1, is now available for testing. This
version fixes many bugs which surfaced in the previous version,
including bugs affecting security, GRANT/REVOKE, and query performance.
Please test-drive this better beta. It's available at
I have posted the latest Derby beta, 10.2.1.2, at
http://people.apache.org/~rhillegas/10.2.1.1-beta/. You can reach the
beta from the 10.2 wiki page
(http://wiki.apache.org/db-derby/TenTwoRelease) and from the 10.2
snapshot description (http://wiki.apache.org/db-derby/TenTwoSnapshot).
Over
As a further refinement on this excellent approach, you can encapsulate
the validator in a function. Something like this:
CREATE TABLE standard (
sizes VARCHAR(32) CONSTRAINT sizes_ck CHECK ( sizeIsLegal( sizes ) )
);
For more information on how to wire Java methods into your DDL and
queries,
I must report today that the restrictions imposed by the beta JDK
license have not been lifted.
As you know, the JDK 6 beta license requires a disclaimer that bars the
use of the code for any productive use. This restriction is meant to
forestall binary incompatibilities with the final, GA
Andrew McIntyre wrote:
On 9/11/06, Rick Hillegas [EMAIL PROTECTED] wrote:
I can see two alternatives for us:
1. Ship 10.2 on the current schedule but do not include the JDBC4
drivers. When run on Java SE 6, Derby 10.2 would continue to expose our
JDBC3 implementation. In addition, we
Geir Magnusson Jr wrote:
I read Rick's note on the 10.2 licensing issue in an archive because of
strange move to the user list, so sorry for the weird quoting :
He said :
I must report today that the restrictions imposed by the beta JDK
license have not been lifted.
As you know, the JDK 6
Geir Magnusson Jr wrote:
Rick Hillegas wrote:
Geir Magnusson Jr wrote:
I read Rick's note on the 10.2 licensing issue in an archive because of
strange move to the user list, so sorry for the weird quoting :
He said :
I must report today that the restrictions imposed by the beta JDK
--
From: Geir Magnusson Jr [EMAIL PROTECTED]
Rick Hillegas wrote:
Geir Magnusson Jr wrote:
I read Rick's note on the 10.2 licensing issue in an archive because of
strange move to the user list, so sorry for the weird quoting :
He said :
I must report
Hi Robert,
I updated the wiki a few days ago because I noticed that the original
dates were clearly stale--we had already slipped by a couple weeks. I
pushed the projected dates out long enough to allow for a couple release
candidates in case our first attempt flops. Discussion about release
The Apache Derby project is pleased to announce a new feature release
of Derby, 10.2.1.6.
Apache Derby is a subproject of the Apache DB project.
Derby is a pure Java relational database engine which conforms to the
ANSI SQL and JDBC standards. Derby aims to be easy for developers
and end-users
Hi Ian,
Two issues block the introduction of a BOOLEAN datatype:
1) We need DRDA support in order to transport this type across our
network layer. I am cautiously optimistic that we will see this type
appear in the DRDA spec early in 2007. So, soon, this issue will not
block us.
2)
The Apache Derby project is pleased to announce a new bug-fix release
of Derby, 10.2.2.0.
Apache Derby is a subproject of the Apache DB project.
Derby is a pure Java relational database engine which conforms to the
ANSI SQL and JDBC standards. Derby aims to be easy for developers
and end-users
Kristian Waagan wrote:
legolas wrote:
Hi
Thank you for reading my post.
is there any support/plan to booean in derby?
Hello Legolas,
This topic has been raised earlier, and an effort was made to add the
boolean data type to Derby. However, this effort stranded because of
lacking support
legolas wood wrote:
Hi
Thank you for reading my post.
We have planned to use Derby embedded for our application internal data storage.
Here I have some questions which any answers could be helpful about them.
- We need highest performance, Should we use stored procedure?
Hi Legolas,
In
Army wrote:
Rick Hillegas wrote:
The next rev of the DRDA spec will define a boolean data type. I'm
expecting to see that rev published in the next couple months.
Any idea if it will define an XML data type, as well?
Army
Hi Army,
Yes, the XML datatype will appear in the upcoming rev
Hi Joe,
The information you need can be found in the following sections of the
Derby Developer's Guide:
o Loading classes from a database
o Derby server-side programming
In addition, the Scores demo, in the codeline, shows you how to declare
and invoke Java methods as functions and
Hi Alexander,
In terms of using a Java Security Manager, there will be better
out-of-the-box support for a secure network server in the next feature
release (10.3). That work is tracked by
https://issues.apache.org/jira/browse/DERBY-2196. Right now, you can
grab a generic policy file from
Dear Derby users,
The next feature release of Derby will close some security holes:
1) When authentication is turned on, only the owner of a database will
be allowed to shut it down, encrypt it, and hard-upgrade it.
2) When you boot the network server as the VM's entry point, the server
Stephen Caine wrote:
Derby User List:
Does anyone have an idea as to when v10.3 might be released? I know
everyone is working hard on this release. We include Derby as part of
our application package and the specific feature, removing a column,
is very important to our users.
Stephen
Hi Shelley,
There is an enhancement request logged for this feature:
http://issues.apache.org/jira/browse/DERBY-672. No-one has picked up
this enhancement request yet--you are welcome to! Most of the code
needed for this feature is actually in the Derby codeline. I think the
blocking issue
It seems to me that the compiler should not think it has enough
information at prepareStatement() time to assign the ? a type of
VARCHAR. That looks like a bug to me.
As a workaround, the following statement gives the compiler enough
information to correctly type the ? parameter. This allows
Hi Sameer,
You might try using a temporary table to hold the values in the IN list.
For more details, see the section in the Derby Reference Manual titled
DECLARE GLOBAL TEMPORARY TABLE statement. Here's an example of this
technique.
Regards,
-Rick
autocommit off;
ij drop table t;
0 rows
Hi Dustin,
Table and column names are called SQL identifiers and, according to the
SQL standard, they are case-insensitive. Like many databases, Derby
stores table and column names in uppercase.
You can get the behavior you want by double-quoting your table and
column names. If you double
Hi Kevin,
I think that Kristian and Bernt have given you the workarounds for this
issue. It is true that Java ADTs were supported in earlier versions of
Cloudscape. However, those ADTs were declared in a non-standard way. ADT
support was disabled before the code was open-sourced as
Don't forget the Derby party at Java One tonight!
Cheers,
-Rick
Rick Hillegas wrote:
Hey folks,
Sun Microsystems is hosting a Derby party at Java One. Here are the
specifics. Hope to see you there!
You are cordially invited to:
An Apache Derby unBoF at JavaONE 2007!
hosted by Sun
Come
The upcoming release of Derby 10.3 will make networked configurations
safer by installing a Java security manager if the user forgets to
install one. This will happen only if the user boots the network server
without installing a security manager. As a result, it will be harder
for hackers to
The Apache Derby project is pleased to announce a new feature release
of Derby, 10.3.1.4.
Apache Derby is a subproject of the Apache DB project.
Derby is a pure Java relational database engine which conforms to the
ANSI SQL and JDBC standards. Derby aims to be easy for developers
and end-users
Williamson, Nick wrote:
Hi all,
In Oracle, it's possible to have an index column that is the result of a
function, for example:
CREATE INDEX index_name ON table_name
(
UPPER(column_name)
);
It doesn't seem possible to do this in Derby. What would be the best way
to mimic this
into the Getting Started Guide. The
Working with Derby Guide was removed in this release.
Laura
On 8/10/07, Rick Hillegas [EMAIL PROTECTED] wrote:
The Apache Derby project is pleased to announce a new feature release
of Derby, 10.3.1.4.
Apache Derby is a subproject of the Apache DB project.
Derby
Hi Mike,
I think the problem is the datatype of the function's return value. The
VARCHAR datatype needs a length. This should work:
CREATE FUNCTION FUNC_NO_ARGS() RETURNS VARCHAR( 100 )
...
Hope this helps,
-Rick
Mike Norman wrote:
latest Derby:
Apache Derby
10.3.1.4 - (561794)
Hi Brandon,
This syntax works in the latest Derby release (10.3.1.4). Are you using
an older version of Derby?
Thanks,
-Rick
Brandon Dohman wrote:
I was wondering what the sql syntax is to drop a column from a derby
database.
i tried this and it gave me the error below: ALTER TABLE
Hi Mike,
Try passing in null as the catalog and schema arguments. The javadoc for
DatabaseMetaData.getProcedures() is a little vague about this.
Hope this helps,
-Rick
Mike Norman wrote:
latest Derby:
Apache Derby
10.3.1.4 - (561794)
Apache Derby Network Client JDBC Driver
10.1.2.1
Hi Brandon,
This is described in the Derby Developer's Guide,
http://db.apache.org/derby/docs/10.3/devguide/ The left pane is a table
of contents--near the top you will see a link for the section on Upgrade.
Hope this helps,
-Rick
Brandon Dohman wrote:
what is the process for upgrading
Hi Kevin,
Derby does support databases stored in jar files. This is described in
the Derby Developer's Guide
(http://db.apache.org/derby/docs/10.3/devguide/) in a subsection called
Accessing databases from a jar or zip file. Just follow these headings
to get to that subsection:
JDBC
Hi Geoff,
Several DatabaseMetaData methods return ResultSets which have a column
named REMARKS. For instance, getColumns(), getTables(), and
getProcedures() return ResultSets which contain a REMARKS column. The
contents of these columns are determined by queries stored in the
following Derby
Hi Geoff,
You're welcome to create a JIRA issue, describing this new feature.
Instructions on how to create a JIRA can be found in the Provide
Feedback section at the top of the following webpage:
http://db.apache.org/derby/derby_comm.html At a minimum, other people
may be able to help you
Hi Paulo,
It doesn't appear to me that you have set ANT_HOME as described in
trunk/BUILDING.txt. That may be part of the problem.
Hope this helps,
-Rick
Paulo Jesus wrote:
I'm building from console.
I use ant ver. 1.6.5. It works fine compiling derby 10.2.2.0.
I keep ant.properties and
Tim Dudgeon wrote:
How do you find out which UNIQUE constraints exist for a table, and
which columns they use?
DatabaseMetaData.getIndexInfo( ... ) can give me the information about
the indexes, but it seems that in Derby a UNIQUE index is not the same
thing as a UNIQUE constraint.
Thanks
distribution archive.
I'm no DITA or HTML guru, but that doesn't seem right. I'm pretty sure
that's a left-over from the environment where Rick (Hillegas) built
the documentation for the 10.3 release...
Hmm, I thought Myrna Van Lunteren was the release manager for the
10.3 release
Alan Burlison wrote:
I have a Java database-side function that does a simple lookup of a
string on a reference table and returns the corresponding integer. If
the string can't be found I want to return NULL, but if I return a
Java null I get a database exception rather than the desired
Alan Burlison wrote:
Rick Hillegas wrote:
It is hard to say where the NullPointerException originates. Could
you post a reproducible test case and the full stack trace from
derby.log?
Umm, it may be my bad, I have the following:
public static int iGoBang() {
int pop = 0 == 0
Hi Rene,
The following ij command will give you the current version of the data
stored on disk. I don't think that this is a documented part of Derby's
api, so this could change in a future release:
values syscs_util.syscs_get_database_property( 'DataDictionaryVersion' );
Hope this helps,
Cloudscape (the codeline which Derby is based on) used to include
user-defined aggregates, which you could declare with a CREATE AGGREGATE
statement. DERBY-672 tracks the effort to put user-defined aggregates
into Derby. It sounds as though you might want to volunteer for this
effort. That
1 - 100 of 927 matches
Mail list logo