|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
Stay one step ahead of the competition. Evaluate and give feedback
on some of the hottest web development tools on the market today.
Make your opinion heard! Click
Here
|
|
#1
September 7th, 2003, 11:35 AM
|
||||
|
||||
|
what about record versions
I need to know when a new version of an record is created and when the old record version will be deleted. I know that concurent transactions create a new record version but I'm so confused about this...
|
|
#2
September 7th, 2003, 04:06 PM
|
||||
|
||||
Re: what about record versions
Quote:
If i understand you want a trigger ? In a trigger you can work with the OLD version and with the NEW version of the record when you modify it . Show me the database structure and what you want to achieve . If it is easier you can contact me on PM in romanian 
|
|
#3
September 8th, 2003, 12:22 AM
|
||||
|
||||
|
it's not about trigger ...
... it's about versioning type of concurent acces of a database.
Other database server use the locking model to resolve conflict between concurent read/write acces, IB/FB use versioning model.
|
|
| Viewing: Dev Shed Forums > Databases > Firebird SQL Development > what about record versions |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
