Is there a jira issue for adding a limit statement (to limit the number
of records returned) to a select statement? I did a jira search but
could find no such issue. I’d like to vote for it.
Hi Jim,
I think DERBY-581 is the issue that tracks this request:
http://issues.apache.org/jira/browse
Hi,
Is there a jira issue for adding a limit statement (to limit
the number of records returned) to a select statement? I did a jira search but
could find no such issue. I’d like to vote for it.
I also searched the mailing list for discussions regarding
this feature, and respo
As a workaround, I changed “generated”
from “always” to “by default”, and insert the root node
with a reference to itself. I’ll detect and treat the
self-referential case as root node in my code. But if anyone has any
other useful ideas, I’d be interested to hear them.
Thanks,
Jim
Hi,
I’d like to create a hierarchical table which
references itself and enforces uniqueness. For example:
create table node (
id int not null generated always as
identity primary key,
name varchar(32) not null,
fk_parent_id int,
> Please open a jira issue for this. If you can provide a standalone repro
> for the problem, that would be helpful.
Raised as
http://issues.apache.org/jira/browse/DERBY-1996
and "Apache JDO TCK" schema attached with small standalone app.
Thanks.
--
Andy
Java Persistent Objects - JPOX
Andy Jefferson wrote:
The schema in Apache JDO is created specifying lowercase identifiers but they
haven't quoted the identifiers so will be stored UPPERCASE in Derby.
If I call
DatabaseMetaData.getColumns(conn, null, "DATASTOREIDENTITY0", null);
it returns in the order of 17ms with the c
I personally consider 3 minutes just to give basic schema information (of a
schema that is *not* particularly big) to be totally unacceptable.
Yes, this sounds like it is way too long.
Can you construct a small standalone test program that demonstrates
the problem? For example, a program along
Hi,
I've been using DatabaseMetaData.getColumns(...) to get lists of existing
columns. The schema is the schema "DATASTOREIDENTITY0" of the Apache JDO
project TCK.
The schema in Apache JDO is created specifying lowercase identifiers but they
haven't quoted the identifiers so will be stored UPP
