On 7/25/2013 2:51 AM, sworddrag...@aol.com wrote:
I'm not sure what you want to say me. "echo 'garbage' > some/random/file"
will also overwrite non-empty files which is more problematic.
Precisely. So do you believe there should be an option to disable echo
command? Or rm command? Or cp
I also have hard time follow...
My answer would be: "yes,"
What is the problem?
On Thu, Jul 25, 2013 at 8:51 AM, wrote:
> I'm not sure what you want to say me. "echo 'garbage' > some/random/file"
> will also overwrite non-empty files which is more problematic.
>
>
I'm not sure what you want to say me. "echo 'garbage' > some/random/file"
will also overwrite non-empty files which is more problematic.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
sworddrag...@aol.com wrote:
> I'm using sqlite3 3.7.9 on Ubuntu 12.04 dev. If the VACUUM command is used on
> empty files it will create a default database (for
> example "touch /tmp/test.txt && sqlite3 /tmp/test.txt VACUUM").
>
> If this behaviour is wanted there should be an option to disable
I'm using sqlite3 3.7.9 on Ubuntu 12.04 dev. If the VACUUM command is used on
empty files it will create a default database (for example "touch /tmp/test.txt
&& sqlite3 /tmp/test.txt VACUUM").
If this behaviour is wanted there should be an option to disable this because
it could destroy
If there is no redundancy to remove then the database size will
remain the same. Vacuum is only really effective after you delete a
large amount of data from a DB.
- Scott
Li, Charles wrote:
> Hi,
> I use the vacuum command on a database, but the size remains the same. What
> should I check?
>
Hi,
I use the vacuum command on a database, but the size remains the same. What
should I check?
Thanks,
Charles Li
7 matches
Mail list logo