Forum Replies Created
-
AuthorPosts
-
Shadow
Member@peterlaursen: I have just donwloaded your ideas regarding views, triggers and stored procs in SQLyog GUI. It's a remarkable article, I'll need some more time to consider its suggestions. But there is a little mistake I would like to point out:
Quote:But SELECTs are always possible, provided you have the necessary privileges to the VIEW itself AND to ย the underlying TABLE as well.This is wrong, no one has to have any rights to the underlying table(s) whatsoever, that's the whole point of views! You may grant a user to add new records to a table provided those records match a certain criterion (view's where clause) but other updates will fail.
Quote:Special rule: If you have a privilege to perform an operation on a view, you don'tneed the same privilege on the underlying tables. That is, if you have the
UPDATE privilege on view v, which is based on table t, you can update v —
assuming that v is updatable. There is no requirement that you have the
UPDATE privilege on t as well.
(MySql 5.0 Views white paper)
Shadow
MemberMySql's command line utility is mysql.exe and mysqld.exe!
Shadow
MemberCommand line solution is: mysql -h your_host -u your_user -pyour_password < your_sql_script_file
Shadow
Member@blankenb: Your case is apparently about a security issue, check whether [email protected] user has the right to connec to the given server without password (does this account exists at all?)!
Shadow
Member2-way sync feature of SQLyog is not a clustering solution! It was designed to bring 2 dbs in sync with one another, that's true, but completely lacks load balancing and automatic update when a change was commited to any of the dbs. What you need is MySql clustering. You'll find articles relating clusters on MySql's website here.
Shadow
MemberRitesh may want to correct me, but SQLyog MAX has still a long way to go… ๐
Shadow
MemberNot necessarily the whole window should be coloured, but a better distinction between differenc connections is welcome!
Shadow
MemberAs far as I'm concerned, you can't stop while fetching data because SQLyog is single threaded app, thus its GUI will not respond while fetching data is in progress.
Why don't you use ODBC from Excel to get data straight from MySql to Excel?
Shadow
MemberNo special setup is needed, just make sure that database structures are the same on all the computers and use the same MySql version. You may use SQLyog's data structure sync tool to ensure the first criterion.
You'll need SELECT, INSERT, UPDATE, DELETE privileges to all tables to be synced.
300k databases are small, even a dial-up connection would be sufficient, although a simple DSL or leased line would be a more reliable method. Whole databases will not be copied (apart from the first sync), SJA uses concat_ws() to generate a checksum for each record to be compared.
SJA is scheduled by OS' built-in scheduler tool, once you are convinced that the sync does what you had expected, then you can leave the job alone.
Shadow
MemberI would be grateful if you notified me of the results! Just in case I run into the same error once again…
Besides, 500 bytes value corresponds to specs as your ISP has a 4.0 and not 4.1.2 or higher.
Shadow
MemberMea maxima culpa, I forgot NTFS ๐ฎ . On Monday I personally deleted an overgrown log file of 6GB…
How do you know he/she is not following our little conversation? ๐
Shadow
MemberNo. I'm good at administering/tuning MySql, but recompilation is a different issue. I believe, it requires more than just changing one variable from 500 to 1000, MySql would have done it otherwise… If I were the ISP, then I would write to MySql and ask for their help, or I would ask for some help on a MySql forum.
Shadow
MemberThre is no way to modify this limit – apart from modifying the source code of MySql. See this feature request. If you use utf-8 encoding, then you may consider choosing another one, as utf-8 uses 3 bytes to store a character.
Shadow
MemberYes, I knew that, but OS restrictions still apply. Most OSs will not allow you to create files larger than 4GB. That's why I wrote that MyISAM wouldn't do, merge tables or InnoDB engine should be used.
Shadow
MemberI agree with Peterlaursen, this error does not seem to have anything to to with SQLyog. MySql forums suggest to decrease field lengths in the given index. As far as I'm concerned, this limit has been imposed to prevent the creation large index entries that would slow down selects and would consume extra storage capacity.
-
AuthorPosts