In a transactional database system, it's entirely possible that once
you're out of space, you cannot drop tables or delete rows, because
doing so will require more space during the course of committing the
transaction.
There are two levels to this. One is if the storage medium is full.
In that ca
You can DROP tables or DELETE all the rows from every table with SQL
queries. That is what Kristof was inferring.
On Oct 14, 2007, at 7:16 AM, Scott Hess wrote:
I think this does imply an ability to delete the entire local
database, which might be a reasonable API addition. Even short of
thi
OK, that's valid, my devil's advocacy is withdrawn.
I think this does imply an ability to delete the entire local
database, which might be a reasonable API addition. Even short of
this case, you could also consider the named databases as part of an
app's database schema in the sense that data cou
As long as the database is readable, I can query all data out of it and
upload them to a backup server via HTTP. While this need not be the most
efficient and secure way to go, there are no software obstacles against.
Better methods may be invented.
Best regards,
Chris
-Original Message-
On 10/14/07, Kristof Zelechovski <[EMAIL PROTECTED]> wrote:
> It is possible to recover from a database full error. You can dump the data
> to a slower device for example. While this action would not make the
> database operable again, you would at least avoid losing data.
This is true in the ge
Note that this is also an issue in Opera's current implementation
test case: http://www.rikkertkoppes.com/other/wf2-repetition-model/
note the legend element ending up halfway the fieldset. It occurs to
that this is unwanted bahaviour, it follows directly from the current wd
though
Regards,
R
On Oct 14, 2007, at 2:03 AM, Henri Sivonen wrote:
...
I don't think "If both attributes are specified, then the ratio of the
specified width to the specified height must be the same as the ratio
of the logical width to the logical height in the image file." solves
any real problem given what b
On 10/13/07, Ian Hickson <[EMAIL PROTECTED]> wrote:
> > Recent discussion at Xiph around http://www.ietf.org/rfc/rfc4281
> > suggests the use of the following parameters:
> >
> > # application/ogg; codecs="theora, vorbis" for Ogg Theora/Vorbis files
> > # application/ogg; codecs="theora, speex"
It is possible to recover from a database full error. You can dump the data
to a slower device for example. While this action would not make the
database operable again, you would at least avoid losing data.
Best regards,
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PR
