Hi Sanja,
My idea is to perform a distributed data system (DDS) to this engine. A DDS
will be composed by at least one group. Each group may involve many MySQL
servers, and each server may belong to more than one group.
So, the best way I've seen is to manage it into 3 system tables: DDE_SERVER,
DDE_GROUP and DDE_SERVER_GROUP.
For example: to subscribe a server into a group, I must: a) insert the
server into DDE_SERVER table, if not exists; b) insert a relation between
the new server and the existent group in DDE_SERVER_GROUP. So, all the group
multicast communication will be proceeded to synchronize all servers.
Sanja, may I send the doc spec to you? (it's better shown in page 11).
Thank you again
Fabricio
-----Mensagem original-----
De: Sanja Byelkin [mailto:sanja@stripped]
Enviada em: sabado, 12 de novembro de 2005 07:09
Para: Fabricio Mota
Cc: internals@stripped
Assunto: Re: RES: System Tables
Hi, Fabricio!
On Fri, Nov 11, 2005 at 11:13:45PM -0300, Fabricio Mota wrote:
> Ok, I'll study these codes.
>
> But I need to create 3 system tables in mysql database. These tables
should
> manage persistent data, and make specific actions (specific code routines)
> when user try to insert, update or delete data into or from them. Do you
> think these codes you adviced me could answer these (new) questions?
I am not sure that it is right decision to add something to mysql
database. If you describe why you need that tables in mysql maybe I Will
agree with you, but now I have bad strong feeling about adding
something to mysql database.
To perform some actions on changing some special tables you have 2
options:
1) use triggers.
2) prohibit access direct access to that tables and use special
commands to update them (like CREATE/DROP PROCEDURE)
[skip]
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Oleksandr Byelkin <sanja@stripped>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Lugansk, Ukraine
<___/ www.mysql.com