AW: AW: AW: Paging performance problem

Hi Rick, good to know.  Regards Gerrit -Ursprüngliche Nachricht- Von: Rick Hillegas Gesendet: Dienstag, 5. Januar 2021 20:00 An: Derby Discussion ; Hohl, Gerrit Betreff: Re: AW: AW: Paging performance problem Hi Gerrit, I'm glad that you found a satisfactory answer to your

AW: AW: Paging performance problem

Gesendet: Montag, 4. Januar 2021 16:43 An: Derby Discussion ; Hohl, Gerrit Betreff: Re: AW: Paging performance problem Hi Gerrit, It's hard to say without seeing the query plans for these scenarios. What query plans do you see when you follow the instructions in the "Working with RunT

AW: Paging performance problem

and data_create_timestamp_key index, the query takes even longer than my originally one (100s ). In addition: I passed a simply SQL query. Wondering if I also can recreate that with JPA/JPQL... Regards, Gerrit Von: Hohl, Gerrit Gesendet: Montag, 4. Januar 2021 15:43 An: Derby Discussion Betreff

Paging performance problem

Hello everyone, we're trying to use OFFSET and LIMIT for paging. But as our tables our growing, we're running in some performance problems we didn't expect. Let's say we have the following structure (the table can also have more columns, but for the sake of simplicity...): CREATE TABLE data

AW: AW: Indexes grow over time insanly big and can't be shrunk

there next time. Regards, Gerrit -Ursprüngliche Nachricht- Von: Rick Hillegas Gesendet: Samstag, 19. September 2020 18:27 An: Hohl, Gerrit ; Derby Discussion Betreff: Re: AW: Indexes grow over time insanly big and can't be shrunk Thanks for the extra information, Gerrit. I don't have an

AW: Indexes grow over time insanly big and can't be shrunk

Hello everyone, I'm sorry, I noticed that only replied to Rick.  Regards, Gerrit -Ursprüngliche Nachricht- Von: Hohl, Gerrit Gesendet: Mittwoch, 16. September 2020 09:21 An: Rick Hillegas Betreff: AW: Indexes grow over time insanly big and can't be shrunk Hello Rick, thanks

Indexes grow over time insanly big and can't be shrunk

Hello everyone, we use Apache Derby v10.14.2.0 in our software and now have a problem with an installation. Every night we perform a compact on all tables - at least the ones which can be shrunk (SYSCS_DIAG.SPACE_TABLE() and SYSCS_UTIL.SYSCS_COMPRESS_TABLE(String, String, Smallint)). Normally

AW: AW: AW: Questions about query execution and optimization

umns without their aliases. Thanks a lot, Rick. That helped me a lot. Regards Gerrit -Ursprüngliche Nachricht- Von: Rick Hillegas Gesendet: Dienstag, 7. Juli 2020 00:48 An: Derby Discussion ; Hohl, Gerrit Betreff: Re: AW: AW: Questions about query execution and optimization Hi Gerrit, One th

AW: AW: Questions about query execution and optimization

ings: I guess you're talking about this here. https://db.apache.org/derby/docs/10.14/tuning/ctun_xplain_style.html Seems like a neat little project on its own... Regards, Gerrit -Ursprüngliche Nachricht- Von: Rick Hillegas Gesendet: Montag, 6. Juli 2020 14:54 An: Derby Discussion ; Hohl, Ger

AW: Questions about query execution and optimization

- Von: Hohl, Gerrit Gesendet: Freitag, 3. Juli 2020 16:22 An: Derby Discussion Betreff: Questions about query execution and optimization Hello everyone, this week I came across a behaviour of Apache Derby which I couldn't explain to myself. I'm using version 10.14.2.0 and the structure

Questions about query execution and optimization

Hello everyone, this week I came across a behaviour of Apache Derby which I couldn't explain to myself. I'm using version 10.14.2.0 and the structure of the database looks like this: CREATE TABLE license ( id BIGINT NOT NULL, [...] ); CREATE TABLE installation ( id

AW: Calling a java function from a trigger

Hello fkalim, hello Rick, just saw your discussion here and I guess the problem is maybe - without having tested it - that you have to use the full qualified name oft the class including the package name. Just by specifying the JAR and the class-name Derby / the class-loader shouldn't be able

AW: Use Apache Derby Network Server with encrypted database

data over network. On 25 August 2016 at 08:47, Hohl, Gerrit <g.h...@aurenz.de> wrote: Hello Peter, hello George, thank you for your 2 mails. And sorry I didn't reply earlier. Yes, I also realized that there is no difference between the embedded and the standalone version. Th

AW: Use Apache Derby Network Server with encrypted database

parameters because you do not know if database has already booted or not. I strongly recommend using SSL to connect to encrypted database ;) On 24 August 2016 at 09:15, Hohl, Gerrit <g.h...@aurenz.de <mailto:g.h...@aurenz.de> > wrote: Hello everyone, I've used Apache Derby f

Use Apache Derby Network Server with encrypted database

Hello everyone, I've used Apache Derby for years now as an embedded RDBMS. BTW: Thanks to all developer doing a great job developing this database system. :-D But now I want to use it as a separate service running on Ubuntu Linux. This is no problem. But I haven't found any