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

Forum Replies Created

Viewing 15 posts - 5,191 through 5,205 (of 7,398 total)
  • Author
    Posts
  • in reply to: Data Sync Only Works When I Use The Wizard #21981
    peterlaursen
    Participant

    “Somewhere in that complete list of clicks and keypresses I gave you is a flaw.”

    I do not think so myself. Once the sceduled job is saved with the Scheduler the 'complete list of clicks and keypresses' are forgotten. The Scheduler only knows what has been saved and nothing else.

    But any DEFINITIVE explanation would be welcome! I also noticed that there are similar issues with MySQL Administrator Scheduled Backup.

    in reply to: Data Sync Only Works When I Use The Wizard #21979
    peterlaursen
    Participant

    aha .. food for thought!

    scheduling “sja myjob.sjajob” does not work. scheduling “myjob.sjajob” does once associations are set.

    I'll add this to the FAQ after some research and experimenting myself!

    However I still thnik is a issue with the scheduler.

    in reply to: Happy New User #21999
    peterlaursen
    Participant

    This 'popup-window' is not resizable. You will find a few more of the kind. That is on the TODO.

    The export as SQL window is 584*669 pixels here. But do yo really mean that is is bigger than your screen?

    but @Ritesh@Manoj: 584*669 would cause a problem with 800*600 screen resolution I think?

    in reply to: Feat. Req: Cell Movement And Scrolling #21997
    peterlaursen
    Participant

    Sorry! My misunderstanding. Was fixed in beta8 allready.

    Can you verify with beta8 or beta9 ?

    in reply to: Feat. Req: Cell Movement And Scrolling #21996
    peterlaursen
    Participant

    A developer of ours informs me that this has allready been solved in the developemnt ree.

    We had a similar report a few days ago.

    next beta with the fix in 1-2 hours!

    in reply to: 5.16 Beta 9 – Migration Toolkit #21995
    peterlaursen
    Participant

    Two more details:

    1) Note that there can only be one column defined as 'default CURRENT_TIMESTAMP' in a MySQL table. If you try to insert more now()'s or CURRENT_TIMESTAMP's as defaults only the first will be effective. The next(s) will silently be converted to 'default 0000-00_00 00:00:00' (at least hat was what happened to me when I tsted this with Acces yesterday)

    2) If you wnat to use the TIMESTAMP defined as

    'default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP' you will have to execute the appropriate SQL statement (ALTER TABLE) after the import. You can do from a 'Notifications Service' job running in the same batch as the Migration. SJA does not have a monkeyman's chance to know if you will use this clause or not!

    See MySQL documentation at:

    http://dev.mysql.com/doc/refman/5.0/en/timestamp-4-1.html

    When we have checked other ODBC sources (Oracle, Interbase, Sybase etc) for similar issues we will of course document it. Maybe even over time implement code that solves most cases 'automatically'

    in reply to: 5.16 Beta 9 – Migration Toolkit #21994
    peterlaursen
    Participant

    I actually I think so!

    The MySQL parser is not very 'precise' in spotting the exact place. That is due to caching, code optimizing etc (actually a lot of code gets rewritten by the MySQL optimizer). It is common that the syntax error is 20-50 characters before the parser says 'stop. I had enough'! And I have seen it much before that.

    Is is not syntax debugging comparable to a compiler/IDE!

    And as far as I can see there are getdate()'s not so far from/before the error message. 'not so far' in MySQL parser terms.

    in reply to: 5.16 Beta 9 – Migration Toolkit #21992
    peterlaursen
    Participant

    Actually the problem that you have with beta9 is becauase we SOLVED it.

    Believe it or not!

    it is 'DEFAULT getdate()' that is the problem. getdate() is not available in MySQL. From the Map option you can enter the MySQL equivalent “now()” or “CURRENT_TIMESTAMP” (they are synonyms).

    Before beta 9 SJA/Migration 'quoted' DEFAULTs. Beta9 does not and you can enter KEYWORDS and FUNCTIONS that MySQL accepts as DEFAULTs.

    Before beta9 there was no way. Any quoted 'string' would raise an error with MySQL Timestamps.

    Some day in the future we may build in the program some small 'conversion tables' for converting from SQL server, Oracle, Sybase etc. But we actually had a user in our ticket system yesterday that needed a usable fix IMMEDIATELY.

    in reply to: Were Are Back! #21958
    peterlaursen
    Participant

    Follow-up: 44 users imported. Hope everything is OK.

    Still wondering where to adjust the counter … 😮

    in reply to: Tab Spaces Setting #21989
    peterlaursen
    Participant

    No there is not …

    .. but that feature has been requested frequently lately.

    it is on the 'nearby TODO list' …

    peterlaursen
    Participant

    The setting is in MySQL configuration itself. The configuration parameter is named “lower_case_table_names”

    Insert this line in the [mysqld] section your my.ini file

    lower_case_table_names=2

    ..and you will get the behaviour you want! You need to restart MySQL for the change to take effect.

    lower_case_table_names=0 means case-insensitive, store as lower-case (default on Windows)

    lower_case_table_names=1 means case-sensitive, store as mixed-case (default on most *nix – except Mac OS-X)

    lower_case_table_names=2 means case-insensitive, store as mixed-case

    However MySQL has confirmed a bug that I reported here:

    http://bugs.mysql.com/bug.php?id=20356

    (but it only affects the 'show create table' statement, not .sql import)

    in reply to: Data Sync Only Works When I Use The Wizard #21977
    peterlaursen
    Participant

    This an issue with the Scheduler itself. It runs as 'execute now' and would probably/likely/certainly also do from commandline.

    Does this FAQ help:

    http://www.webyog.com/faq/27_34_en.html

    Often this behaviour is explained if you run the job from a user account of a human user, that does not have a password.

    Try go through the job details from the Scheduler (from Control Panel) interface itself.

    The file “abc” is the job file – and it is OK (if not it would not 'execute now'). You did not specify an extension, so it has none. It does not need either. SJA does not use the extension for any purpose. You can use any extension as described here:

    http://www.webyog.com/faq/27_74_en.html

    in reply to: Data Sync Only Works When I Use The Wizard #21975
    peterlaursen
    Participant

    Suggestions are welcome .. but I am not sure I understand this one!

    I DO understand that if more jobs running simutaneously are trying to use the same session file results are unpredictable.

    We could build a checksum of some kind with the details of the job and use this checksum for naming the session file. Similar to what we do with the autocomplete TAG-files. Or use the current TIMESTAMP for naming the session file. Something like that?

    in reply to: Images To Database? #21973
    peterlaursen
    Participant

    You should use a BLOB, MEDIUMBLOB or LONGBLOB column (BLOB = Binary Long OBject).

    SQLyog has a special BLOB-viewer that support the most common graphics formats.

    in reply to: Nasty Bug Found In Text Entry: V5.14 And V5.15 #21962
    peterlaursen
    Participant
    Quote:
    At least put in a switch somewhere in preferences!

    We will discuss that.

    BTW: Please observe too that also functions are evalutated.

    http://webyog.com/faq/8_116_en.html

Viewing 15 posts - 5,191 through 5,205 (of 7,398 total)