Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantAnd it is the same problem wiht MySQL 5.02 (alpha)
ParticipantQuote:but these is a multiple Primary keyThat's in my opinion no good.
“multiple primary key” – what's that ?
I've seen that before but I believe it's a very unhealthy construction
(Actually my own photography database uses the same construction. The program that I use is ThumbpsPlus http://www.cerious.com and the program unfortunately won't work if I change it)
You kan create “unique indexes” like that, but a primary key must be one field.
Actually I think it's a minor flaw in MySQL that it allows for it.
What you get is not a “multiple primary key” but multiple “primary key”s – and that's makes no sence in my opinion
– only ONE key can be “primary” just like there can only be ONE winner in a game!
Correct me if I'm wrong!
ParticipantAre you sure that the mysql version is 4.2 ??
Never heard about anything higher then 4.1.9 in en 4.x build …..
Here is a quote from the mysql manual
Quote:ou can specify DATETIME, DATE, and TIMESTAMP values using any of a common set of formats:As a string in either 'YYYY-MM-DD HH:MM:SS' or 'YY-MM-DD HH:MM:SS' format. A “relaxed'' syntax is allowed: Any punctuation character may be used as the delimiter between date parts or time parts. For example, '98-12-31 11:30:45', '98.12.31 11+30+45', '98/12/31 11*30*45', and '98@12@31 11^30^45' are equivalent.
As a string in either 'YYYY-MM-DD' or 'YY-MM-DD' format. A “relaxed'' syntax is allowed here, too. For example, '98-12-31', '98.12.31', '98/12/31', and '98@12@31' are equivalent.
As a string with no delimiters in either 'YYYYMMDDHHMMSS' or 'YYMMDDHHMMSS' format, provided that the string makes sense as a date. For example, '19970523091528' and '970523091528' are interpreted as '1997-05-23 09:15:28', but '971122129015' is illegal (it has a nonsensical minute part) and becomes '0000-00-00 00:00:00'.
As a string with no delimiters in either 'YYYYMMDD' or 'YYMMDD' format, provided that the string makes sense as a date. For example, '19970523' and '970523' are interpreted as '1997-05-23', but '971332' is illegal (it has nonsensical month and day parts) and becomes '0000-00-00'.
As a number in either YYYYMMDDHHMMSS or YYMMDDHHMMSS format, provided that the number makes sense as a date. For example, 19830905132800 and 830905132800 are interpreted as '1983-09-05 13:28:00'.
As a number in either YYYYMMDD or YYMMDD format, provided that the number makes sense as a date. For example, 19830905 and 830905 are interpreted as '1983-09-05'.
As the result of a function that returns a value that is acceptable in a DATETIME, DATE, or TIMESTAMP context, such as NOW() or CURRENT_DATE.
Which timestamp format do you use: text or number ?
You are sure that the timestamp isn't identical for those records that don't copy ?
(if the chosen timestamp format is too short!)
Further the timestamp format has changed from different wysql-versions. So using timestamp as a PK if not the mysql versions are totalaly identical is not wise.
Also note that in mysql the “resolution” of the timestamp is only seconds and not milliseconds ore smaller “timeslices”.
So on a big corporate database it's likely that there are records having identical timestamps. Since it takes almost a minute to syncronize in your case it must be a big database ….
Participantno, I now think that Ritesh was right in the first place.
the sql-statement that causes mysql 5.0.2 to crash is
Quote:describe `dbname`.`tablename`– nothing else.
Mysql 5.0.2 also crashes when issuing that statement from “MySQL Query Browser” from http://www.mysql.com
I now also can reproduce it with yog 4.0.0 RC.
So it undoubtedly is an issue wiht the 5.0.2 alpha.
However it's somewhat confusing that it does not always happen …
My serverversion is max-nt.
I tried with and without “named pipes” and with and without debugging, but it makes no difference here.
Participant… just a correction
It is ONLY the combination {yog 4.0.2 + Mysql 5.0.2} that makes this happen. Not other comninations of yog a.
>>>
It is ONLY the combination {yog 4.0.2 + Mysql 5.0.2} that makes this happen. Not other comninations of yog and MySQL.
ParticipantCONFIRMED !
With my setup the description of the error is truly correct with yog 4.0.2 + Mysql 5.0.2 both installede on a WinXP (Danish) SP2
It works correctly with ver MySQL 4.1.9
The yog 4.0.0 RC1 (that I staill have installed) does not show this behaviour – not with mysql 5.0.2 either.
It is ONLY the combination {yog 4.0.2 + Mysql 5.0.2} that makes this happen. Not other comninations of yog a.
Actually this is the first time I have been able to crash my mysql server !!!
What would happen if it is a remote server, and not a local MySQL ?!?
>> Ritesh
THERE IS NO QUERY AT ALL –
this is correct
Quote:clicking on the table name within SQLyog crashes MySQLParticipantIs it a server of your own or one at an ISP/webhotel ??
in the URL field on the tunnel-tab just write the path to the SQLyogTunnel.php-file RELATIVE to your webroot-driectory- like
http://www.mydomain.xyz/SQLyogTunnel.php
or
http://ip.ip.ip.ip/SQLyogTunnel.php
if the “theecoop.com” -folder is your webroot folder and SQLyogTunnel.php is there.
What the folder name is oin the server file hierachy doesn't matter – if it's only YOUR webroot folder. The webserver and it's configuration will take care of that.
Participantsqlyog ver. 4.0.2 should be a ” fix for this issue”. Isn't it ?
ParticipantYou are using SJA – is that the Linux version or the version “built in” sqlyog (for windows) ??
SJA is a SYNCRONIZATION TOOL, that means you syncronize data from one running Mysql server to another. That means that you must have the two running mysql servers accessible (local or remote). Thats what SJA is for, and NOTHING ELSE !!!
You can run the backup command from the sql-pane in sqlyog or from any command-line tool.
Or from the GUI in sqlyog. Provided that you run windows.
However the BACKUP command is in my opinion not very usual as EXPORTING to a sql-file.
(how would you actually use the .frm and .MYD -files ? )
No, its probaly locked by the system because its in use!! Mysql is not Access and you can't just copy files like that …
ParticipantI believe it must be some sort of networking or server problem!
PhpMyAdmin is running on the same machine as as the MySQL server, so here is no networking issue!
What happens if you install sqlyog on the machine running the MySQL-server. Can you connect then ?
Also check that the “skip-networking” parameter is not set in the my.ini -file.
ParticipantYes, but still it's a database CLIENT. It's not a progrram with an integrated DB and GUI. There is only the methods available for working on the BD as supplied by the DB vendor (mysql). For the dicussion it does not matter whether you connect with the C-api as sqlyog does or any other method. Sqlyog is not part of the database.
I find it harzardeous to DELETE or UPDATE a record if it is not uniquely identified. For databases used by personal websites and the like you might be able to control it, but with big corporate databases – no!
But I agree that other ways of uniquely identifying a record than the PK (and I can only think of an unique index) should be possible.
Participantread this thread and try the 4.02 beta …
ParticipantAs I have said a couple of times I belive that an UNIQUE INDEX or a PRIMARY KEY should be used for identifikation of records in case of deletions and syncronizarion. Yog right now only supports a PK.
But there MUST be either UNIQUE INDEX or a PRIMARY KEY. If none of those are present, you can't be sure that there are not identical records ….
ParticipantYou could tell a little bit about what happens ! Does it just time out, or do you have an error message ?
But it's likely that the ISP/webhotel won't let you connect from remote on port 3306 (a lot of ISP's are plagued by DOS attacks on their MySQL server prots at this time. So has my own and they closed the port. If that's the case you can use the tunnelling features of sqlyog entreprise.
ParticipantThe table must have a Primary Key if you want to delete a record using sqlyog.
-
AuthorPosts
