Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 15 posts - 6,751 through 6,765 (of 7,398 total)
  • Author
    Posts
  • in reply to: New ODBC-import Nothing :-) #18553
    peterlaursen
    Participant

    gmail system returned it because of “illegal attachment”. it was a normal zip!

    I mailed you a DL link instead. Did not get that ?

    in reply to: New ODBC-import Nothing :-) #18551
    peterlaursen
    Participant

    delivered to your gmail!

    in reply to: Wot diffrence b/w 'Index' and Foreign Key? #18549
    peterlaursen
    Participant

    @MohsinAli

    Sorry .. I was mistaken on one point.

    It is the opposite way around. You can CASCADE on UPDATE and DELETE with the PK definition. That means that you can change a category-name or delete a category and the referring values will be automatically updated or deleted.

    in reply to: Wot diffrence b/w 'Index' and Foreign Key? #18547
    peterlaursen
    Participant

    BTW … this must be a bug (see image)

    I tried to change 'deep ocean' to 'deep-deep-deep ocean

    latest SQL from history pane:

    select count(*) from `madvarer` where `mytext`='redfish' and `kategori`='fish' and `specifik beskrivelse`='Lives in deep-deep ocean'

    It uses alias with SQL on line 1. The SQL on line 3 does not use an alias for that result-column and does not raise error.

    It is not beacuase of the relationsship.

    Problem is the same with resultset from this query:

    select mytext as wetryagain from madvarer;

    raises err.msg “unknown column 'wetryagain' in where clause when trying to edit.

    in reply to: Wot diffrence b/w 'Index' and Foreign Key? #18546
    peterlaursen
    Participant

    to be honest …

    you really don't need FK's for this example. There are other ways to do it. But using FK has some advantages

    – for instance (if defined properly) it wont let you delete or change a category-item that is still in use by the other table. And you can define the FK ins such a way (using the CASCADE keyword) that a category-item is automatically deleted, when the last item referring to it is deleted (if you want that).

    in reply to: Wot diffrence b/w 'Index' and Foreign Key? #18545
    peterlaursen
    Participant

    Just created this simple showcase for you to show an example of how you can use a FK (same data as above)

    in reply to: Wot diffrence b/w 'Index' and Foreign Key? #18543
    peterlaursen
    Participant

    Very briefly:

    1) an index is a “sorted list” of fields from a table. It speeds up MySQL performance to have an index built that matches the searches (WHERE-expressions and ORDER BY-expressions for instance) you use often. If there is no index available for a certain query, MySQL must read all data – if there is an appropriate index, MySQL will only need to read the index.

    There can be a lot of indexes with a table (the exact number depends on MySQL-version and storage engine).

    2) a “unique index” is an index where each value in the index corresponds to exactly one row in the table.

    3) a “Primary Key” is a special case of a unique index. There can only be one Primary Key. An autoincrement integer column is often used as a Primary Key. It's is almost always a good idea to have a Primary Key (speeds up certain MySQL internal functions)

    4) there is another special case of indexes called “fulltext index'es”. They are only available with MyISAM tables. You use it for finding substrings of string variables using the SQL-operator MATCH. If you have a string in your DB somewhere like 'Bunny is my favorite pet” an appropriate fulltext index would let you find this string when MATCHing with 'bunny' or 'favorite'. It would even let you find it when MATCHing with “bonny” and “favourite”.

    5) A foreign key is an index that uses data from another table. To use foreign keys you must use a storage engine that supports it. InnoDB storage engine is mostly used for this. MyISAM tables do not support FK's yet (it is planned for MySQL ver 5.1)

    If you have to tables with content

    table content

    *******************'***

    food (hamburger, pizza, beer, wine, tea, milk, cola, sandwich, beef, redfish)

    categories (drinks, fastfood, meat, fish)

    … you can use a Foreign Key to map

    'hamburger','pizza' and 'sandwich' from table “food” to 'fastfood' in table “categories”

    'beer',wine','tea',milk' and 'cola' from table “food” to “drink” in table “categories”

    'beef' from table “food” to 'meat' in table “categories”

    and finally 'redfish' from table “food” to 'fish' in table “categories”.

    then you can use the “categories”-table to let MySQL search in the “food”-table

    But there are books and internet resources abot all this. And the MySQL documentation not to forget!

    in reply to: new 4.07 will not start #18541
    peterlaursen
    Participant

    Good evening Mr. Sherlock Holmes 😎

    If you need a Remote Desktop -program you could check Qnext http://www.qnext.com.

    It's has never conflicted with anything on my machine (it is java-based – runs in “sandbox”).

    But of course that is on WinXP …

    But since 4.06 works with PC Aanywhere, they should be able to make 4.07 do it too, I think!

    in reply to: "Show Results In Text" broke with 4.0x #18530
    peterlaursen
    Participant

    Yes this is correct

    Quote:
    ill only show all data up to the row limit specified in SQLyog's preferences

    This is also correct

    Quote:
    In previous versions, if you chose “View Data”, and had text mode enabled, the table rows would be displayed as text.

    But with a SELECT-statement I can choose only SOME columns and SOME rows to be shown i RESULT-pane.

    I don't have the imagination that anyone would need to show a complete table (all rows & all colums) in text. But since you do, you can request a “show table data in text” option.

    The major improvement with 4.x is that you can edit data from result-view!

    in reply to: "Show Results In Text" broke with 4.0x #18527
    peterlaursen
    Participant
    Quote:
    Not for me, this is a bug.

    Show results in text only has effect on result-tab not data-tab!

    I disagree with you! Nothing should be changed back here! It's a major improvement!

    Data-tab always show ALL data in table, result-tab the result of last SELECT-query.

    You could do a “select * from …” , choose “show result in text” and it works from result-tab.

    But I would not mind an option like “show table data in text” – though I would probably never use it myself.

    in reply to: new 4.07 will not start #18538
    peterlaursen
    Participant

    I have no chance to go deeper into this (don't have a 2K).

    And probably they have left office in Bangalore now ( they have to feed the tigers! 😀 ).

    But undoubtedly they will look into it tomorrow (saturday is working day for them!)

    in reply to: new 4.07 will not start #18535
    peterlaursen
    Participant

    No problem here on XP SP2 (Danish)

    I believe it is a 2K – issue. The various ServicePack-levels with win-2K is a mess!

    What is your SP-level and localization ?

    An “ordinary” 2K or 2K-server ?

    Did you try the 4.07 BETA and RC-releases ?

    in reply to: Ordered SQLyog back in 03-04 #18532
    peterlaursen
    Participant

    It is all to read from here

    http://www.webyog.com/sqlyog/upgrade.html

    If your version is 4.x the answer is yes – if it is 3.x the answer is no.

    From menu: help .. about displays version number.

    in reply to: "Show Results In Text" broke with 4.0x #18525
    peterlaursen
    Participant

    from menu: edit .. show results in text .. works here.

    You did not simply overlook that option ??

    But the option is not saved to .ini-file when closing SQLyog.

    The grid view is implemented to make it possible to delete or update data from RESULT.

    The new DATA and RESULT-pane as of 4.0 is a major improvement in my opinion!

    in reply to: still problems with \ character in PK #18321
    peterlaursen
    Participant

    Let us conclude on this long rather messy thread ..

    Most important

    1) There was a defect with some of my data having double “end-of-string” ('') characters

    2) There was a bug with SJA that could cause failure to sync when PK was built on a char/varchar -column containing the backslash ( '' ) -character (such as a windows' filename)

    3) Sometimes the GUI would fail to drop using a tunneled connection when opening an existing XML-file with a tunnel spec. from GUI

    It's all fixed with 4.07. No reason for concern with SQLyog 4.07.

    It has been very diffucult here to “sort out” or “isolate” each issue. Ritesh and I have been working on this intensively for almost a week. My PM-mailbox is filled up with correspondance about this… But it was worth it

    😀

Viewing 15 posts - 6,751 through 6,765 (of 7,398 total)