[Still Learning]

IMPORTANT FOR NEWBIES

After much frustration (mostly due to my own inexperience), I've “discovered” the issues alluded to here. FWIW sqlyog is turning out to be a great tool (frankly I don't know how anyone ever would administer a dbase without a similar tool) even if the aforementioned TABLE NAMES USING CamelCaps WITH MYSQL RUNNING ON WINDOWS proved to be a “bugger” of a bug (i.e. make sure you name/rename the tables all lowercase to use this product with mysql running on a windows machine).

Moreover, be aware you must create your own index (and in the proper order) to create some FK relationships (I don't know if this is a requirement of mysql or even a best practice), as well as making all the attributes the same in BOTH the two fields being related.

While I'm not an expert by any means, I hope this helps any and all . . .

[Still Learning]

.. but what does 7 bytes of disk storage cost today? 🙂

>>>>> obviously you are right, thanks though for pointing it out as this is the sort of thing us newbies wouldn't realize until later given the preponderance of advice in sql books to minimize size etc. — any other top of the mind “real-world” best practices you can suggest??

[Still Learning]

I assume so, in that when I set two columns to Timestamp datatype, one defaults (automatically) to CURRENT_TIMESTAMP and the other to:

0000-00-00 00:00:00

Yet, — and I know from the manual — you can set two columns to record a date/time in the same table. So, how do I set one to record the time when the row was created and one to record the time the row was (last) updated?

[Still Learning]

1) one byte is required for the ” – ” sign

that makes sense, so if I set INT unsigned it will default to 11 and if not then default to length 10

2) I practically always make an autoincrement PK a BIGINT UNSIGNED .. but probably 'overkilll' in most situations!

correct me if I am wrong, but it is possible to change (increase specifically) the size later on (as data needs require) without much difficulty right? Also, in theory, better performance is obtained from a smaller number, all other things being equal?

[Still Learning]

Sorry, I meant, drag one column (with exactly matching attributes) over top of another table's column in order to create a FK reference

What about indexes defined on that column? or Foreign Keys referencing it?

>>>>>>I've played with each of these settings without luck as yet

What if tables have different default charsets and the charset/collation is not explicitly defined for the column?

>>>>>>> The only thing notable I can find is that when I right click >> View advanced properties on any of the new tables there is no info displayed whatsoever whereas the same process on existing tables lists a great deal of info (however, double click to open either new or old table and then clicking on advanced properties lists EXACTLY the same attributes for each table.

[Still Learning]

“I add a new table it refuses to let me make relationships with/to it claiming a “Table Mis-match. Please refresh the canvas” “

I have not encountered that! But we can check with the code of course what exactly condition raises exatly this error mesage!

1) Can you describe in detail how to reproduce it?

I have a schema I imported from mysql 5. I create a new table (via right click on schema background). I try to drag and drop a column to or from the new table to an old table (either way) but am greeted with “Table mismatch. Please refresh the canvas”. I try refreshing via F5 and/or via right click on canvas. No joy. I create two new tables. I try to drag and drop from one of the new tables to another but get the same error message. (((Is there a way to refresh in the object view or ????)

2) Does save SCHEMA .. program restart .. open SCHEMA remove this message? NO

Does close and reopen connection? NO

[Still Learning]

Thanks for your prompt reply, using RENAME in the object browser works well enough (though it requires a refresh and series of clicks to show up on the schema).

However, a major prob I am coming across is that when I add a new table it refuses to let me make relationships with/to it claiming a “Table Mis-match. Please refresh the canvas”. Yet the prob does not go away even after I refresh, nor after I change both Tables Tabletype to InnoDB (via the right hand button); nor after I then refresh again etc.

As such, 1.) Is there any suggestions you have to address the above? 2.) Is there anyway to set the default table type (ie. when creating a new table) to InnoDB (or another type) so this issue never becomes a factor?

Thanks in advance

Mike

[Author]

Posts