I don't know if I just can't find it but there doesn't seem to be the equivalent of NOBACKUP as there used to be in DBISAM. Is there a chance of it making a comeback so my disk doesn't get littered with .OLDs


Roy Lambert

Roy,

<I don't know if I just can't find it but there doesn't seem to be the equivalent of NOBACKUP as there used to be in DBISAM. Is there a chance of
it making a comeback so my disk doesn't get littered with .OLDs>

I subscribe this! Also tired of deleting .olds here and there.

Tiago.

Roy,

<< I don't know if I just can't find it but there doesn't seem to be the
equivalent of NOBACKUP as there used to be in DBISAM. Is there a chance of
it making a comeback so my disk doesn't get littered with .OLDs >>

There isn't one now, but I'll see what I can do.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Thank you. I know disks are enormous these days but the post was prompted by the fact that I just deleted c4Gb of .Olds

Roy Lambert

Roy,

<< Thank you. I know disks are enormous these days but the post was prompted
by the fact that I just deleted c4Gb of .Olds >>

Well, the reason that it wasn't done initially is that eventually ElevateDB
will have DDL versioning, and that may preclude being able to add the
NOBACKUP.  IOW, the backups will be the versioning that allows you to
rollback a table (or tables) to a previous version of the catalog.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< Thank you. I know disks are enormous these days but the post was prompted
>by the fact that I just deleted c4Gb of .Olds >>
>
>Well, the reason that it wasn't done initially is that eventually ElevateDB
>will have DDL versioning, and that may preclude being able to add the
>NOBACKUP. IOW, the backups will be the versioning that allows you to
>rollback a table (or tables) to a previous version of the catalog.

In that case can I have a NOVERSIONING flag please? I really don't want that amount of garbage being kept. Others may, and I can see a use for it as a replacement for my copying sideways when I'm about to do something dangerous, but I prefer it to be under my control.

Roy Lambert

Roy,

<< In that case can I have a NOVERSIONING flag please? I really don't want
that amount of garbage being kept. Others may, and I can see a use for it as
a replacement for my copying sideways when I'm about to do something
dangerous, but I prefer it to be under my control. >>

You're forgetting that you have no way of knowing which catalog version
belongs to which table files.  Therefore, copying around files does not tell
you all that you need to know about what needs to be restored in the case of
a failure.

At any rate, I'll see about an option to turn it off when it does get
introduced.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Ahh, but you're forgetting that I do this before I carry out any substantive operation, and if it goes wrong I just restore the lot catalog included. If it goes right I delete the folder and move on.

Roy Lambert

Roy,

<< Ahh, but you're forgetting that I do this before I carry out any
substantive operation, and if it goes wrong I just restore the lot catalog
included. If it goes right I delete the folder and move on. >>

I'm speaking in terms of all users, not just yourself.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>I'm speaking in terms of all users, not just yourself.

OK I accept that they're not up to my high standards

Roy Lambert