On Fri, Oct 28, 2005 at 01:09:43PM +0200, Mario Splivalo wrote:
> I'll go trough my code, it's been a while since I touched it, I'll write
> some documentation and I'll inform the comunity. Thnx for the pointouts.
And thank _you_ for proposing to do this. If everyone contributes
their discoveries
On Thu, 2005-10-27 at 11:51 -0400, Andrew Sullivan wrote:
> Well, AFAIK Oracle itself offers no replication, either. If you want
> it, you have to buy a license for it. Which means it's an add-on.
> Heck, most Linux distributions' kernels don't offer support for
> network cards: they're an add-
On Thu, Oct 27, 2005 at 02:21:15PM +0100, Richard Huxton wrote:
> So - if your statement contains something non-deterministic that isn't
> catered for in Mysql's code then it will break.
>
> At it's simplest - if I write a function my_random() and then do:
> UPDATE foo SET a=1 WHERE b < my_rand
On 10/27/2005 8:34 AM, Mario Splivalo wrote:
Postgres itself offers no replication.
Oracle itself offers no replication.
IBM DB2 itself offers no replication.
Yet most of the products out there for Oracle, DB2 and PostgreSQL are
far better than what I read here:
http://dev.mysql.com/do
On Thu, Oct 27, 2005 at 02:34:13PM +0200, Mario Splivalo wrote:
>
> Postgres itself offers no replication. You could achive some sort of
> replication by restoring the parts of WAL files, but that's rather
> inconvinient. Then, if you want to replicate your data in any way, you
Well, AFAIK Oracle
On 10/27/2005 4:22 AM, Mario Splivalo wrote:
I see no point in blatantly putting 'other' products such shape. Pgsql
offers no replication at all, you need to use slony (wich is also a poor
replacement for a wannabe replication), or some other commercial
products. What about 2PC? What about linki
On 10/27/2005 4:22 AM, Mario Splivalo wrote:
On Wed, 2005-10-26 at 12:09 -0400, Jan Wieck wrote:
>
You must have missed the FAQ and other side notes about replication in
the MySQL manual. Essentially MySQL replication is nothing but a query
duplicating system, with the added sugar of taking
Mario Splivalo wrote:
On Wed, 2005-10-26 at 12:09 -0400, Jan Wieck wrote:
You must have missed the FAQ and other side notes about replication in
the MySQL manual. Essentially MySQL replication is nothing but a query
duplicating system, with the added sugar of taking care of now() and
some oth
On Thu, 2005-10-27 at 06:21 -0400, Andrew Sullivan wrote:
> On Thu, Oct 27, 2005 at 10:22:41AM +0200, Mario Splivalo wrote:
> > offers no replication at all, you need to use slony (wich is also a poor
> > replacement for a wannabe replication), or some other commercial
> > products. What about 2PC?
On Thu, Oct 27, 2005 at 10:22:41AM +0200, Mario Splivalo wrote:
> offers no replication at all, you need to use slony (wich is also a poor
> replacement for a wannabe replication), or some other commercial
> products. What about 2PC? What about linking the databases from
Slony is in fact a communi
On Wed, 2005-10-26 at 10:19 -0500, Scott Marlowe wrote:
> But, the next time someone says that slony is a toy add on, and MySQL
> has REAL replication, point them to THIS page on the same blog:
>
> http://ebergen.net/wordpress/?p=70
>
> In short, it basically shows that MySQL replication is incr
On Wed, 2005-10-26 at 12:09 -0400, Jan Wieck wrote:
> >
>
> You must have missed the FAQ and other side notes about replication in
> the MySQL manual. Essentially MySQL replication is nothing but a query
> duplicating system, with the added sugar of taking care of now() and
> some other non-de
On Wednesday 26 October 2005 17:44, Scott Marlowe wrote:
> On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
> > hi,
> > i was in a minor flame war with a mysql guy - his major grouse was that
> > 'I wouldnt commit mission critical data to a database that needs to be
> > vacuumed once a week'.
"Bath, David" <[EMAIL PROTECTED]> writes:
> you wrote (2005-10-26 17:00)
>>> Sybase/MS-SQL's check constraint model asserts the constraint
>>> BEFORE the trigger, which discourages you from attempting to>
>>> check and handle meaning of data!
>> Er, doesn't PG do it that way too?
> Well, it work
Tom,
After I wrote
> > Sybase/MS-SQL's check constraint model asserts the constraint
> > BEFORE the trigger, which discourages you from attempting to>
> > check and handle meaning of data!
you wrote (2005-10-26 17:00)
> Er, doesn't PG do it that way too?
Well, it works for me! In this case (wit
On Wed, 2005-10-26 at 11:12, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
> >> i was in a minor flame war with a mysql guy - his major grouse was that
> >> 'I wouldnt commit mission critical data to a database that needs to b
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
>> i was in a minor flame war with a mysql guy - his major grouse was that
>> 'I wouldnt commit mission critical data to a database that needs to be
>> vacuumed once a week'. So why does pg need vacu
On 10/26/2005 11:19 AM, Scott Marlowe wrote:
On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
hi,
i was in a minor flame war with a mysql guy - his major grouse was that
'I wouldnt commit mission critical data to a database that needs to be
vacuumed once a week'. So why does pg need vacu
On Wed, 2005-10-26 at 11:09, Jan Wieck wrote:
> On 10/26/2005 11:19 AM, Scott Marlowe wrote:
>
> > On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
> >> hi,
> >> i was in a minor flame war with a mysql guy - his major grouse was that
> >> 'I wouldnt commit mission critical data to a database
On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
> hi,
> i was in a minor flame war with a mysql guy - his major grouse was that
> 'I wouldnt commit mission critical data to a database that needs to be
> vacuumed once a week'. So why does pg need vacuum?
Oh man oh man. After reading the ar
On Tue, 2005-10-25 at 23:45, Kenneth Gonsalves wrote:
> hi,
> i was in a minor flame war with a mysql guy - his major grouse was that
> 'I wouldnt commit mission critical data to a database that needs to be
> vacuumed once a week'. So why does pg need vacuum?
The absolutely funniest thing about
On Wednesday 26 Oct 2005 11:52 am, Bath, David wrote:
> > This guy is not worth arguing with.
> D'Accord!
thanks all for the clarification. in case anyone is interested in the
original conversation it is here:
http://ebergen.net/wordpress/?p=83
--
regards
kg
http://www.livejournal.com/users/
"Bath, David" <[EMAIL PROTECTED]> writes:
> ... Note that Sybase/MS-SQL's
> check constraint model asserts the constraint BEFORE the trigger, which
> discourages you from attempting to check and handle meaning of data!
Er, doesn't PG do it that way too?
regards, tom lane
On Wed, 26 Oct 2005 15:14, Tom Lane wrote:
> Kenneth Gonsalves <[EMAIL PROTECTED]> writes:
> > (A MySQul guy said, not Kenneth)...
> > 'I wouldnt commit mission critical data to a database that needs to be
> > vacuumed once a week'.
My two-penneth worth...
I wouldn't commit mission cri
On Wed, Oct 26, 2005 at 10:15:17AM +0530, Kenneth Gonsalves wrote:
> i was in a minor flame war with a mysql guy - his major grouse was that
> 'I wouldnt commit mission critical data to a database that needs to be
> vacuumed once a week'.
The use of the word "commit" is amusing, considering that
Kenneth Gonsalves <[EMAIL PROTECTED]> writes:
> i was in a minor flame war with a mysql guy - his major grouse was that
> 'I wouldnt commit mission critical data to a database that needs to be
> vacuumed once a week'.
This guy is not worth arguing with.
> So why does pg need vacuum?
Every data
hi,
i was in a minor flame war with a mysql guy - his major grouse was that
'I wouldnt commit mission critical data to a database that needs to be
vacuumed once a week'. So why does pg need vacuum?
--
regards
kg
http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வா
27 matches
Mail list logo
