On 03/12/16 12:50, Hamish Moffatt ham...@risingsoftware.com
[firebird-support] wrote:
>
> I'm also seeing idle transactions in MON$TRANSACTIONS sometimes. That
> is presumably the cause of my big issue, which is that I am reading
> back old data from the db.
OK, here's where I'm confused. The
On 03/12/16 00:59, 'Thomas Steinmaurer' t...@iblogmanager.com
[firebird-support] wrote:
> I also see a ton of connections on MON$ATTACHMENTS from the same thread
> in my application (MON$REMOTE_PID, MON$REMOTE_ADDRESS both the same)
> which also makes no sense.
Closing a connection implicitly
Olaf wrote 02.12.2016 10:43:
>Also I can do the following:
>
>Priority in steps of 1
>
>ID 10 Prio 1
>ID 20 Prio 2
>ID 23 Prio 3
>ID 11 Prio 4
>
>Now the user can Set the ID 23 to Prio 2, how can I realize this
without a loop?
>
>Update table set prio = newprio(1) where id = 20;
.. and can I order all active records completly?
(without a loop)
Don't manage the records during your direct update, manage the order
records via a AFTER UPDATE trigger...
Using a "separator" in the priority range is good, you can use it to
manage the scope of the changes required. You
IDENTITY in FB3 uses the same logic as previous versions (trigger and
generator), only it is hidden from the user. Behind the scenes it is doing
that.
If you don't find the better solution, here is how you can get generator
name for the Primary Key (IDENTITY):
(change CUSTOMER to your table
Nico Speleers - Carfac BVBA nico.spele...@carfac.com [firebird-support]
a écrit :
> How can I reset an autoincrement field in firebird 3 ? I used identity to
> make an autoincrement field.
::=
RESTART [ WITH ]
I only use the property Identity to make an autoincrement field and I don't
make use of generators. Therefore 'How can I reset an autoincrement field in
firebird 3 ? I used identity to make an autoincrement field' ?
Nico Speleers
Analyst
Carfac bvba
Driving on experience
Rijksweg 53
How can I reset an autoincrement field in firebird 3 ? I used identity to make
an autoincrement field.
Thanks.
Nico Speleers
Analyst
Carfac bvba
Driving on experience
Rijksweg 53
9680 Maarkedal
Tel. +32 55 23 00 00
Fax +32 55 31 00 95
nico.spele...@carfac.com
Hi
i do not read your whole info but maybe you need to use case statement
e.g your 3 update statements can be changed fro:
Update table set prio = newprio(1) where id = 20;
Update table set prio = prio – 1 where prio < newprio;
Update table set prio = prio + 1 where prio > newprio;
to
On 02/12/16 20:59, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] wrote:
> 02.12.2016 8:56, Hamish Moffatt ham...@risingsoftware.com [firebird-support]
> wrote:
>> I understand that the idle statement
>> means they have been prepared but not executed, but this shouldn't be
>> possible
02.12.2016 8:56, Hamish Moffatt ham...@risingsoftware.com [firebird-support]
wrote:
> I understand that the idle statement
> means they have been prepared but not executed, but this shouldn't be
> possible in my application source (prepare has never failed, and I
> always execute).
Yes, but
.. and can I order all active records completly?
(without a loop)
Update table set prio = 1 to n where prio is not null order by prio?
Von: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Gesendet: Freitag, 2. Dezember 2016 10:44
An:
Okay,
I would simply change the prio new in steps of 10.
Also I can do the following:
Priority in steps of 1
ID 10 Prio 1
ID 20 Prio 2
ID 23 Prio 3
ID 11 Prio 4
Now the user can Set the ID 23 to Prio 2, how can I realize this without a
loop?
Update table set prio =
13 matches
Mail list logo
