Also is "full outer join" statements supported?
On Thu, Nov 15, 2018 at 11:09 AM Alex O'Ree wrote:
> Thanks Rick
>
> I also noticed that the wording and ordering of limit and offset for
> select statements is way different in derby.
> Postgres style: select * from table
:
> Hi Alex,
>
> Thanks for compiling this list of issues. Some comments inline...
>
> On 11/14/18 1:22 PM, Alex O'Ree wrote:
> > Greetings. I'm looking for some kind of migration guide and for things
> > to watch out for when migration an application to derby.
> >
>
ork around it.
On Thu, Nov 15, 2018 at 4:38 PM Peter wrote:
> Hello Alex,
>
> May I ask why are you moving to Derby? What are your pain points with
> Postgres?
>
> Kind Regards
> Peter
>
>
> Am 14.11.18 um 22:22 schrieb Alex O'Ree:
> > Greetings. I'm looking f
Greetings. I'm looking for some kind of migration guide and for things to
watch out for when migration an application to derby.
Since i haven't found one yet, i decide to write down and share some of my
notes on the things I've ran into so far:
DDL - From postgres, there's lots of differences.
-
.com/questions/1793979/registering-multiple-keystores-in-jvm
>
> Hope this helps,
> -Rick
>
> On 12/11/18 6:20 AM, Alex O'Ree wrote:
>
> The derby security guide for enabling tls connection supports only loading
> the keystore location/password from the global
components.
There is a NetworkServerControl#getCurrentProperties() method. Can i inject
the javax.net.ssl properties through there before starting the server?
On Mon, Nov 26, 2018 at 7:10 PM Rick Hillegas
wrote:
> On 11/26/18 3:58 PM, Alex O'Ree wrote:
> > My primary use case
Is there a particular reason we can't do indexes on long varchar columns?
Is it possible to (from the same JVM) using the embedded driver in
combination with allowing remote access on the same database? I'm having
some issues getting it to function, seems like it's one or the other.
perfect, thanks!
On Mon, Nov 26, 2018 at 7:10 PM Rick Hillegas
wrote:
> On 11/26/18 3:58 PM, Alex O'Ree wrote:
> > My primary use case is to use an embedded derby within my webapp for
> > storage and whatnot. I also have another requirement to provide
> > localhost (and p
My primary use case is to use an embedded derby within my webapp for
storage and whatnot. I also have another requirement to provide localhost
(and possible remote access) to the database via jdbc connection. I know
how to get derby up and running programmatically in embedded mode and with
the
yup, definitely a blob. it looks like the like operator doesnt work for
blobs, or maybe i need a cast or some function to the conversion
On Mon, Sep 30, 2019 at 6:50 PM Rick Hillegas
wrote:
> On 9/30/19 9:18 AM, Alex O'Ree wrote:
>
> I have a use case where i have string data stored
I have a use case where i have string data stored in a blob and i want to
perform a query similar to
select * from table where column1 like '%hello world%'
It doesn't look like this is possible with derby out of the box. Is there a
way to create a function that calls a java function or something
Perfect, thanks
On Tue, Nov 5, 2019 at 8:57 AM Rick Hillegas
wrote:
> On 11/5/19 4:03 AM, Alex O'Ree wrote:
> > I have a use case where by I add a bunch of rows, export then in an
> > archive, then delete all the rows and repeat for weeks or months on end.
> > Are
I have a use case where by I add a bunch of rows, export then in an
archive, then delete all the rows and repeat for weeks or months on end.
Are there any maintenance procedures I should be running after each purge?
Postgres and mssql has some functions to tell it to recover disk space and
llegas
> *Sent:* Sunday, February 7, 2021 4:11 PM
> *To:* Derby Discussion ; Alex O'Ree <
> alexo...@apache.org>
> *Subject:* Re: Slow mount times
>
>
>
> I don't know of any special trace flags for this. Maybe something will
> turn up in derby.log if you set
I've got a process that creates a bunch of temporary indexes, then does
some work, then drops the indexes. All of these indexes are on different
tables but in the same database. During the drop the indexes phase, i
frequently get dead lock warning messages, each drop index statement seems
to be
for derby, there doesn't appear to be any indication of what's
going on.
On Sun, Feb 7, 2021 at 2:12 PM Alex O'Ree wrote:
> That's perfect, although from my testing, it seems like more than 4 files
> indicate an unclean shutdown. I just want to alert the user that it may
> take some time t
Sometimes when my app starts, it can take several minutes to initialize the
database. Is there a way to find out whats going on? There isn't much log
output. I have overridden derby.stream.error.method but other than the the
startup message, I don't have much to go on.
Is there perhaps a startup
where it
> was running. The engine then needs to reconstruct the state of the
> database by replaying many recovery logs. To gracefully exit Derby, you
> need to explicitly shutdown Derby as described here:
> https://db.apache.org/derby/docs/10.15/devguide/tdevdvlp20349.html
>
>
19 matches
Mail list logo
