ALL RECORDS + DELETE SELECTION,
or selecting all records and deleting them in User Mode
logs "delete" action for each record in the journal file.
TRUNCATE TABLE, on the other hand, has its own single action in the journal
file.
"Truncate" clears the address table, whereas "Delete" does not.
the
> I am using truncate. I just want to make sure that by using this command then
> then running MSC repair,
> I will get new fast indices for these tables and table space will be correct.
> If one uses delete command and deletes
> most of the records table space is screwed up. That was my real
On Tue, Apr 4, 2017 at 2:04 PM, Douglas von Roeder via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> It's a command whose function is to clear all the tablespace allocated to
> records in a given table along with the associated indexes.
>
> Delete selection is used to delete one or more records,
<4d_tech@lists.4d.com>
Cc: Douglas von Roeder <dvonroe...@gmail.com>
Subject: Re: delete or truncate
Steve:
Very good point about a transaction.
Reading Chuck's posting, I got the impression that this would be done on an
"as needed" basis.
To me, Truncate table is sort of
nal Message-
> From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Timothy
> Penner via 4D_Tech
> Sent: Tuesday, April 04, 2017 1:16 PM
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Cc: Timothy Penner <tpen...@4d.com>
> Subject: RE: delete or truncate
>
sts.4d.com>
Cc: Timothy Penner <tpen...@4d.com>
Subject: RE: delete or truncate
> I like the TRUNCATE TABLE command, but I'm thinking this cannot be used
> within a transaction.
" No transaction must be underway in the process executing TRUNCATE TABLE. If
this if the case, t
Chuck:
I'd go with truncate.
It's a command whose function is to clear all the tablespace allocated to
records in a given table along with the associated indexes.
Delete selection is used to delete one or more records, ensuring that
indexes and relational integrity constraints are enforced for
7 matches
Mail list logo
