Add a SQL command to support feature LOG_SIZE_LIMIT=32

[IntensiveH2]

Currently, in latest version of H2, you can add a setting like LOG_SIZE_LIMIT=32 in the connection string but unfortunately you can't change this settings by SQL command like SET LOG_SIZE_LIMIT 32.

Do you plan to add this feature?

Thanks.

[Noel Grandin]

Personally, no.
But if you feel like having a bash at it yourself, the place to start is
in the
org.h2.command.Parser
class, in the
private Prepared parseSet()
method.

[IntensiveH2]

Can you explain why because others parameters are defined as SQL command?

Thanks.

[Thomas Mueller]

Hi,

Why do you need LOG_SIZE_LIMIT?

I don't think I want to support it as a SQL statement.

Regards,
Thomas

> --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To post to this group, send email to h2-da...@googlegroups.com.
> To unsubscribe from this group, send email to
> h2-database...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/h2-database?hl=en.
>

[Thierry Legrain]

Hello Thomas,

It's related to a previously thread named " Automatically compact databases from time to time (as a background process)"
Currently, as use the connection syntax, but I think that it should be useful to set it on the fly.
I'm agreeing it's not a mandatory feature.

Thanks.
Thierry.

[Thomas Mueller]

Hi,

Probably you mean MAX_LOG_SIZE, there is a SQL statement for that:
http://h2database.com/html/grammar.html#set_max_log_size

LOG_SIZE_LIMIT is about something else, it's about rolling back
transactions that were not committed since a long time. I guess I
should rename this setting.

Regards,
Thomas

[IntensiveH2]

Hi,

No, I speak about  LOG_SIZE_LIMIT (about rolling backtransactions).

Also, by default why LOG_SIZE_LIMIT is not equal to MAX_LOG_SIZE.

Thanks.

[Thomas Mueller]

Hi,

FYI: I will probably remove the (quite new) feature LOG_SIZE_LIMIT,
because it doesn't always work correctly (for example, locks are
released unexpectedly).

Regards,
Thomas

> --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/h2-database/-/VdhBnit9z2YJ.