Hello, comments inline. Regards, Karen.
I checked up in the mean time, and it does not make a truly consistent backup
of MyISAM - it locks all tables - yes, ALL tables - and then copies the
files. Given that MyISAM doesn't support transactions, that means that any
transactions (that
- Original Message -
From: Karen Abgarian a...@apple.com
This however means that the resulting snapshot will be consistent.
The fact of taking a backup really cannot create more consistency
than what the application has by design. If the application inserts
related rows in say two
snip
If that's all you did, you indeed 'removed the default NULL' but did not
specify another default. Hence, if you don't explicitly specify a value in
your
insert statement, the insert can not happen as the server doesn't know what
to
put there and is explicitly disallowed from leaving the
Hello people!
I'm developing a system that needs to find places around a point informed by
the user!
I have a lot of place in a db and all of them has the coordinates
information ( gotten by google maps api geocoding );
When I use mbrcontains to find all places into a polygon (circle with the
Hi! Inline, again.
On Jun 9, 2011, at 4:58 AM, Johan De Meersman wrote:
True, but I have never seen an application that checks for inconsistency in
it's tables. Making sure all users have stopped using the app ensures no
in-flight transactions, and then you have a consistent database -
snip
A single table is always consistent. Data inconsistency occurs in sets of
interrelated tables, in other words, on the database level.
[JS] Not even a single table is always consistent (unless there is
transactions). Consider a single transaction that consists of two steps:
1. Delete
On Thu, June 9, 2011 11:59, Jerry Schwartz wrote:
snip
A single table is
always consistent. Data inconsistency occurs in sets of
interrelated tables, in other words, on the database level.
[JS] Not even a single table is always consistent
(unless there is
transactions). Consider a single
