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

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Out Of Range Value? #22886
    Paula
    Member
    peterlaursen wrote on Nov 7 2006, 10:42 PM:
    This column is an integer.

    Do you have date exceeding the range as described here:

    http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

    “All integer types can have an optional (non-standard) attribute UNSIGNED. Unsigned values can be used when you want to allow only non-negative numbers in a column and you need a larger upper numeric range for the column. For example, if an INT column is UNSIGNED, the size of the column's range is the same but its endpoints shift from -2147483648 and 2147483647 up to 0 and 4294967295.”

    You could then make it a BIGINT …

    No, none of those figures would be larger than 8 characters. Changing it to BIGINT didn't work anyhow.

    in reply to: Joining/optimizing Nightmare #22850
    Paula
    Member

    The two tables are on my harddrive (400G:cool:. I'm running MySQL on my machine only. My syntax is simple:

    SELECT BIRTH.*, NAME.*

    FROM BIRTH INNER JOIN NAME on (BIRTH.LAST3 = NAME.LAST3) and (BIRTH.FIRST3 and NAME.FIRST3);

    When I check the CPU usage, it's going back and forth from about 7 pct to 22 pct.

    peterlaursen wrote on Oct 24 2006, 12:18 PM:
    two chances …

    * upgrade the server (or your resources on it)

    * upgrade the connection

    This is a single query and it is not SQLyog that is slow. SQLyog is patiently waiting for data to arrive! But try to include a “LIMIT 1000” for instance and measure the time. Your JOIN syntax could be wrong resulting in an astronomic rows returned.

    Also Check Task Manager. How much CPU is used? What is the network transfer rate?

    in reply to: Text File Import Problem : Bad Name? #22806
    Paula
    Member
    peterlaursen wrote on Oct 19 2006, 12:58 AM:
    The problem is that the table name 'brthdate.txt' in not valid wilt MySQL before version 5.1.

    You will have to use the mapping option to rename the table to something that is supported.

    Oracle, SQL server etc. conform to standard SQL in respect to table naming. MySQL only does from version 5.1.

    Great, thanks!

Viewing 3 posts - 1 through 3 (of 3 total)