Re: Unique ID's across multiple databases

2010-09-13 Thread Kiss Dániel
Well, that would be the plan, yes. :-) Anyway, I'll get over the problem sooner or later. :-) On Mon, Sep 13, 2010 at 8:46 PM, Jerry Schwartz wrote: > >-Original Message- > >From: Kiss Dániel [mailto:n...@dinagon.com] > >Sent: Monday, September 13, 2010 11:49 A

Re: Unique ID's across multiple databases

2010-09-13 Thread Kiss Dániel
;From: vegiv...@gmail.com [mailto:vegiv...@gmail.com] On Behalf Of Johan > De > >Meersman > >Sent: Monday, September 13, 2010 7:27 AM > >To: Kiss Dániel > >Cc: Max Schubert; mysql@lists.mysql.com; replicat...@lists.mysql.com > >Subject: Re: Unique ID's across multip

Re: Unique ID's across multiple databases

2010-09-13 Thread Kiss Dániel
; >> One bad connection will break the chain, though, so in effect you'll be > >> multiplying the disconnecting rate... > >> > >> I think you'd be better of with a star topology, but MySQL unfortunately > >> only allows ring-types. This is gonna req

Re: Unique ID's across multiple databases

2010-09-13 Thread Kiss Dániel
ing rate... > > I think you'd be better of with a star topology, but MySQL unfortunately > only allows ring-types. This is gonna require some good thinking on your > part :-) > > > On Mon, Sep 13, 2010 at 12:28 PM, Kiss Dániel wrote: > >> This is actually more for fai

Re: Unique ID's across multiple databases

2010-09-13 Thread Kiss Dániel
, 2010 at 12:03 PM, Johan De Meersman wrote: > > > On Sun, Sep 12, 2010 at 9:45 PM, Kiss Dániel wrote: > >> offset + increment thingy is good if you know in advance that you'll have >> a >> limited number of servers. But if you have no idea that you will have

Re: Unique ID's across multiple databases

2010-09-12 Thread Kiss Dániel
You may be right. I'm not arguing that offset + increment is working. I'm just wondering if that's the optimal solution when you do not know how many servers you will have in your array in the future. In my view, the offset + increment thingy is good if you know in advance that you'll have a limit

Unique ID's across multiple databases

2010-09-12 Thread Kiss Dániel
Hi, I'm designing a master-to-master replication architecture. I wonder what the best way is to make sure both databases generate unique row ID's, so there won't be ID conflicts when replicating both directions. I read on forums about pro's and con's using UUID's, also about setting the *auto-inc

Different versions are the same?

2002-07-17 Thread Kiss Dániel
Hi, I've downloaded mysql-max-4.0.2-alpha-win.zip (Anyway, the size of this file is the same as mysql-max-4.0.1-alpha-win.zip) When I unzip this file and start to install it, I can see in the setup window that it is MySQL-max-4.0.1 What is the problem. Guys at MySQL did a mistake, or I downloa

MD5

2002-06-20 Thread Kiss Dániel
Hi everyone, Can anyone tell me how to create an MD5 checksum on a file. I tried to do this by using the MySQL MD5 function, but it does not work on too big files (above 650MB), even if I set max_allow_packet size very big. Is there any small program to do this, anyway? Thx Daniel -

Re: database modelling tool

2002-06-13 Thread Kiss Dániel
Try the Zeos Database Designer. It could be pretty good, but unfortunatelly it's full of bugs, and there's no newer version a long time ago. http://sourceforge.net/projects/zeoslib/ At 13:03 2002.06.13.s +0300, you wrote: >Hello, > >Is there any database modelling tool for mysql? > > >-- >Your

Re: not able to edit table:((

2002-06-11 Thread Kiss Dániel
Greetings, Stop the MySQL server and check the table files. I think they are read only if you use Win32, or under Linux the user 'mysql' does not have the write right to the tables or its directories In the last case: chmod 660 * and/or chown mysql:mysql * At 12:39 2002.06.11. -0400, you wro

Foreign keys in query optimization

2002-06-10 Thread Kiss Dániel
I studied the MySQL and InnoDB manual, but I did not find anything about the internal usage of foreign keys. I mean that I would like to know if foreign keys are used for query optimizations or functions like that. Because I think foreign keys should be used not only for keeping the data integ

Re: InnoDB foreign key constraints

2002-06-10 Thread Kiss Dániel
First of all the referenced key must be on PRIMARY KEY. But I've seen in your table definition a quite strange thing. You have a UNIQUE and an ORDINARY key definition on the same field. Here: ... > UNIQUE KEY `name_id` (`name_id`), <- THIS IS THE FIRST DEFINITION > UNIQUE KEY `comp_name` (`

Re: InnoDB Hot Backups... ALL OR NOTHING ???

2002-06-06 Thread Kiss Dániel
First of all, there are many aspects of your problem. 1. The InnoDB uses transaction safe table types, and uses the log files to restore if anything goes wrong during the tsanasction. So it is almost impossible to have a permanent database error, that cannot be repaired by InnoDB itself. If My

Re: sub-queries

2002-06-06 Thread Kiss Dániel
I'm sorry to disappoint you, but subqueries are NOT supported int any MySQL version, yet. You can read the MySQL manual about it. You can find there when and how it will be implemented. Bye Daniel At 21:39 2002.06.06. +0200, you wrote: >Lo all, > >are sub-queries supported on mysql-ma

Re: SV: building tree view in mysql?

2002-06-06 Thread Kiss Dániel
This problem is already solved in Oracle. It it the CONNECT BY PRIOR statement which recursively queries a table. The good news is that I read in the MySQL manual, that this feature will be implemented in MySQL in the Real Near Future :-). (MySQL manual: "1.8.2 Things That Must be Done in the Re

Are FOREIGN KEYs used?

2002-06-06 Thread Kiss Dániel
I studied the MySQL and InnoDB manual, but I did not find anything about the internal usage of foreign keys. I mean if I define a foreign key it is good for me, because the InnoDB engine does not let the database to get integrity errors. But I think the foreign key definitions could be used in

Re: WinZeos and Transactions

2002-06-04 Thread Kiss Dániel
If WinZeos you've written about is the Zeos Database Objects (http://www.zeoslib.org), then I think I know the solution for your problem. First of all you don't have to BEGIN a transaction because when using an InnoDB connection, you always have an apened transaction, and when you close it by C