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

Forum Replies Created

Viewing 15 posts - 3,226 through 3,240 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25659
    peterlaursen
    Participant

    ok .. then it is probably an issue with Windows 2000!

    We will need to debug on such system, I guess!

    Thanks for the information!

    in reply to: #25657
    peterlaursen
    Participant

    please also tell:

    1)

    does the CREATE/ALTER TABLE dialogues display charsets?

    2)

    what does “select * from information_schema.character_sets” return?

    This may be a server issue (that we have seen similar some times when a 5.x server has been installed on top of a previous version and this upgrade was done incorrectly).

    in reply to: #25656
    peterlaursen
    Participant

    btw:

    1) what is your LOCALE setting? Czech, Slovenian, Polish … ?

    2) if it happens with specific files please zip and att,ach an example.

    in reply to: #25941
    peterlaursen
    Participant

    We do not seem to be able to import excel file directly with that driver. Driver sends message 'ensure that file exists'.

    Are you mapping the file in Access) If yes it is Accces that locks the file so that the driver cannot access it! And then it is no new issue, because also with older access-drivers for older Office versions it was not possible to migrate a mapped/linked file. You will need to import to Access, save as .mdb, close access and now you can migrate.

    I think we cannot help if Access locks the file. Access is not a 'database server' allowing multiple clients to connect – it is a 'flat file' database implementation.

    Please explain in detail what you do! (screenshots are good!)

    in reply to: #25655
    peterlaursen
    Participant

    strange ..

    what is your OS? any other idea? Are you sure the file is a text file and not a binary file?

    Anyway I have another issue with RC2. This dialogue pops up when I select 'import from csv'.

    [attachment=833:errmsg.gif]

    reason is of course that the last file used does not exist any more.

    However after clicking OK the import dialogues opens with CHARSET option enabled-

    [attachment=834:dialogue.gif]

    in reply to: #25944
    peterlaursen
    Participant

    idea is OK …

    but that would take that favorites where moved to a database (as SQLite) and not implemented as a folder tree in the file system on the machine where it runs.

    My best suggestion at the moment is that you name favorites using a prefix/suffix or create a 'subfolder tree' for every connection.

    Do you experience perfomance issues (if so how many 'favorites' do you have and how 'deep is the folder tree?)? Or is it primarily a matter of overview?

    in reply to: #25940
    peterlaursen
    Participant

    yes .. 2007 of course and not 2008!

    I think we need to include this driver in our testsuite!

    Thanks for pointing to it!

    in reply to: #25938
    peterlaursen
    Participant

    “odbc driver for Excel” .. there was a very old Excel driver for office95/97 that never worked properly! i was not aware that they reintroduced in Office 2008 (please confirm: it is office 2008?)

    I do not have this software option here right now. But we have when office opens tomorrow morning!

    in reply to: #25936
    peterlaursen
    Participant

    OK .. we will have a look at this tomorrow with the same setup (driver version, source file type etc.).

    You did not tell the SQlyog version i think? Please …..

    As regards a 'post migration SQL statement': actually an excellent idea!

    For now you can use a batch file (or a simple application) to execute 1) sja 2) the 'post migration SQL statement' from a seperate program.

    http://webyog.com/faq/content/27/35/en/can…-same-time.html

    in reply to: #25934
    peterlaursen
    Participant

    did you try a google search on that error? There seems to be quite a lot!

    http://www.google.com/search?client=opera&…-8&oe=utf-8

    in reply to: #25932
    peterlaursen
    Participant

    1)

    It will save to the installation folder if you do not specify a path.

    Try specifyiing the full path to the jobfile like “c:pathtojobfile.xml”.

    You do this by using the 'explorer' icon in the wizard. Write access to the installation folder may be restricted.

    in reply to: #25930
    peterlaursen
    Participant

    1)

    One possibility: this DUMP does not contain the CREATE DATABASE statement. Did you check this option when exporting?

    It looks like the 'use' option was checked but the 'create database' option was not. See attached image (6.16 export dialogue)

    [attachment=829:expoptions.gif]

    Try creating the database `character`manually before running the script.

    2)

    If there is not supposed to be a database named `character` at all, then to reply to this we will need more information:

    >> What program was used for generating the DUMP file? SQLyog or something else? If SQLyog what version – if something else what then?

    >> Server versions where you export and import.

    >> Could you zip and attach a small example DUMP that throws this error?

    in reply to: #25903
    peterlaursen
    Participant

    We allready have the option to export as Excel XML. This will export data as well as formatting options for the spreadsheet columns/cells.

    But spreadsheet formatting is not quite data typing! It will read the content of cells only:

    This (simple) SQL

    CREATE TABLE `aa` (

    `id` bigint(20) NOT NULL,

    `aa` varchar(50) default NULL,

    `bb` bigint(20) default NULL,

    PRIMARY KEY (`id`)

    ) ENGINE=InnoDB DEFAULT CHARSET=utf8

    will with an empty table generate

    id

    aa

    bb

    and with one row of data (1,unix_timestamp(),unix_timestamp()) inserted

    id

    aa

    bb

    1

    1203005487

    1203005487

    Neither “Number” nor “String” are exact SQL datatypes – they are Excel formatting options only. And what about indexes? and ENGINE and CHARSET parameter (not to mention AUTO_INCREMENT, TIMESTAMP propertes as discussed here recently etc.).

    I do not think that was the request! I think the topic starter wants a one-to-one transformation between SQL and XML!

    in reply to: #25780
    peterlaursen
    Participant
    DonQuichote wrote on Feb 14 2008, 02:20 PM:
    I am not adding anything technical to this discussion, but have a question about it. Is a connection also repaired when executing a batch of SQL statements? In that case, does it open a new connection to the server? The reason I ask is that I use SQL variables a lot in my “repeatable database build” scripts. For those scripts, failing half-way is better than repairing with a new connection (because those variables are lost in the new connection).

    yes, it does. In version 6.2 we will support transactions in batch jobs, and when that option is enabled, the reconnect wrapper will be disabled. For a similar reason actually: reconnecting will 'loose pointers' to the transaction log and only what was executed after reconnect will be committted.

    So from 6.2 you may simple use that option (table engines that do not support transactions will simply ignore)

    in reply to: #25913
    peterlaursen
    Participant

    You may also try the PSPad editor.

    Basically I think that 'Wordpad' is a poorly maintained program that has not been properly updated since Windows 98.

    I am surprised it did not work in Exel, but if version is Excel 95 or 97 that would explain. Microsoft only fully supported Unicode from Windows 200 and Office 2000.

Viewing 15 posts - 3,226 through 3,240 (of 7,398 total)