underlying database concept) look like?
Seun Osewa
PS: I should want to post my ideas too for review but more
experienced/qualified people should come first
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
uarantees atomic, consistent, durable
write)
COMMIT NOSYNC; --> (sacrifice durability of non-critical transaction
for overall speed). So, the question is what people, especially those
who have done DBMS work, think about this!
Seun Osewa.
---(end of broadcast)-
e.g. - that helps ALL transactions) is likely to be
> simpler than having everything be a special case.
I think if database programmers have it,
they will use it to optimize their applications.
Aside from increased speed there is the possibility people
will just get to do some thi
[EMAIL PROTECTED] (Tom Lane) wrote in message news:<[EMAIL PROTECTED]>...
> Christopher Browne <[EMAIL PROTECTED]> writes:
> > In the last exciting episode, [EMAIL PROTECTED] (Seun Osewa) wrote:
> > So I want to ask, "what if databases have a 'COMMIT NOSYNC;&
quot;rela-
tional way", to think of data in form of sets of tuples rather than
tables or lists or whatever. I mean, though its elegant and based
on mathematical principles I would like to know why its the _right_
model to follow in designing a DBMS (or database). The way my mind
sees it, shoul
I have tried, twice, to download the evaluation version of the alphora
product for testing and it doesn't work. Guess there would be a lot
to learn from playing with it; the product is more than a RDBMS
Regards,
Seun Osewa
[EMAIL PROTECTED] (Lauri Pietarinen) wrote:
> That is, in f
would the
underlying model be knowing how redundant and imprecise language can
be? Tell what we may have missed.
Seun Osewa
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
