On 02/22/12 17:49, ik wrote:
On Wed, Feb 22, 2012 at 13:34, Alex Peshkoff peshk...@mail.ru wrote:
On 02/22/12 00:14, ik wrote:
Hello,
For a long time now, I have an idea for a feature, that I gave it a
name of Timeout records
On Tue, Feb 21, 2012 at 23:32, Leyne, Sean s...@broadviewsoftware.com wrote:
The idea is to have a scheduler for records that on timeout can call a
trigger.
Many existed databases (such as Oracle, MS SQL Server and MySQL) contain
a much wider idea, of task scheduler, while my idea is
22.02.2012 11:05, ik wrote:
Sorry, but I do not understand the difference. Can't you add such task
to a Server Manager ?
Just one problem: there is no Server Manager for Firebird.
--
SY, SD.
--
Virtualization
On 02/22/12 00:14, ik wrote:
Hello,
For a long time now, I have an idea for a feature, that I gave it a
name of Timeout records
(http://idkn.wordpress.com/2012/02/20/timeout-records-feature-request/).
Long before I'll ever try to report a feature request, I wish to have
a discussion about
On Wed, Feb 22, 2012 at 13:34, Alex Peshkoff peshk...@mail.ru wrote:
On 02/22/12 00:14, ik wrote:
Hello,
For a long time now, I have an idea for a feature, that I gave it a
name of Timeout records
(http://idkn.wordpress.com/2012/02/20/timeout-records-feature-request/).
Long before I'll
22.02.2012 14:49, ik wrote:
I think that at least task scheduler such as the databases I mentioned
above have, can help a lot in this case, even if we do not have the
tmeout record feature.
As a developer you, probably, know, that there is no point to invent a wheel
and
duplicate already
On Wed, Feb 22, 2012 at 15:58, Dimitry Sibiryakov s...@ibphoenix.com wrote:
22.02.2012 14:49, ik wrote:
I think that at least task scheduler such as the databases I mentioned
above have, can help a lot in this case, even if we do not have the
tmeout record feature.
As a developer you,
22.02.2012 15:13, ik wrote:
And some data tasks require to act according to time
rules.
Such as?..
At the moment, for doing this, you constantly require a daemon and not
a cron based program to constantly access the database and change
data.
For example?..
Wouldn't it be better if
ik [2012-02-22 18:32] :
But Oracle and MS, do think that their DBMS can provide such tasks.
Even MySQL (that I don't really think that it's true DB) have this
feature (but lack more important features).
but PostgreSQL don't
it exists an external tool
22.02.2012 18:32, ik wrote:
Queues that are specific for time, like Task Queues that can start
for example at 10:00:25 pm but no longer then 10:05:40 pm that day .
I never heard about such queries. Could you provide a practical example?
How would you go with that ?
I would go back to
I can't understand the objection. The only think that I do see here
are objections without explaining why. Why such type of features will
be bad ?
Why time based data manipulation are not good for databases but should
be external ?
Don't get me wrong, if I'll understand why, I will write
ik skriver:
Queues that are specific for time, like Task Queues that can start for
example at 10:00:25 pm but no longer then 10:05:40 pm that day . Let's
say you have 5,000 tasks like that on queue. Each of them in different
time scale and period. Cron is not the answer. Would you run your
The idea is to have a scheduler for records that on timeout can call a
trigger.
Many existed databases (such as Oracle, MS SQL Server and MySQL) contain
a much wider idea, of task scheduler, while my idea is different.
I do not like your proposal.
First, it would require that the database
13 matches
Mail list logo
