--- Scott Hess <[EMAIL PROTECTED]> wrote:
> - for newly-created files, create them during the transaction. If
> the transaction rolls back, delete the file. If the transaction
> commits, leave them alone.
>
> - for deleted files, leave them in place. If the transaction
> commits, delete the
--- Yves Goergen <[EMAIL PROTECTED]> wrote:
> On 08.09.2007 21:06 CE(S)T, Joe Wilson wrote:
> > Are you able to store this file in the database itself as a BLOB?
>
> No, its an input file that I'm processing and saving the results in the
> database. When processing and database import are
On 9/7/07, Yves Goergen <[EMAIL PROTECTED]> wrote:
> I'm currently using a transaction for this on the database side and
> rolling it back if the file cannot be deleted. But what if the file is
> gone and then SQLite says it doesn't accept my records? Since we're
> inside a transaction, integrity
In general, you have to do something like:
- for newly-created files, create them during the transaction. If
the transaction rolls back, delete the file. If the transaction
commits, leave them alone.
- for deleted files, leave them in place. If the transaction
commits, delete the files. If
On 08.09.2007 21:06 CE(S)T, Joe Wilson wrote:
> Are you able to store this file in the database itself as a BLOB?
No, its an input file that I'm processing and saving the results in the
database. When processing and database import are successful, the file
must be deleted so that it won't be
On 9/7/07, Yves Goergen <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> in a scenario when multiple operations need to be transactionally
> synchronised, I have a file that must be deleted when the database
> records are added successfully, but the database operations must be
> rolled back, if the file
--- Yves Goergen <[EMAIL PROTECTED]> wrote:
> in a scenario when multiple operations need to be transactionally
> synchronised, I have a file that must be deleted when the database
> records are added successfully, but the database operations must be
> rolled back, if the file cannot be deleted.
>
On 9/7/07, Yves Goergen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in a scenario when multiple operations need to be transactionally
> synchronised, I have a file that must be deleted when the database
> records are added successfully, but the database operations must be
> rolled back, if the file
Hi,
in a scenario when multiple operations need to be transactionally
synchronised, I have a file that must be deleted when the database
records are added successfully, but the database operations must be
rolled back, if the file cannot be deleted.
I'm currently using a transaction for this on
9 matches
Mail list logo