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

Forum Replies Created

Viewing 15 posts - 2,926 through 2,940 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26740
    peterlaursen
    Participant

    “net stop monyog” from

    *start menu .. run

    * or from a commandline, if you think it is shorter! “net start monyog” to start again.

    There is no interface to the Windows Service manger in MONyog itself.

    in reply to: #26735
    peterlaursen
    Participant

    Actually you can dump SQLite data with a client. I think they will import to MySQL for instance. I did this once I remember (but at that time we did not store quite as many counters).

    Every row of data collected is defined with a 'timestampID' PK column. The time information for every timestamp id is in another table, and unix_timestamps are used. So you will need JOINs on the timestamp table and will need to convert unix_timestamps to human readable values. That should not be a problem for users with high SQL level (but the grouped HISTORY display involved very tricky queries actuallly!).

    Also if you should want to import to another system you will probably prefer one database only (or at least only one per connection/server). With SQLite we have more databases per server because SQLite is locking database-level.

    Anyway an export/backup option to a RDBMS that simplifies the schema for easier generation of user queries/user defined analysis is definitely a very interesting idea!

    in reply to: #26739
    peterlaursen
    Participant

    I think with this example you should move the table that is now in lower left corner to upper left position. Then I think it will be easy to rearrange.

    But anyway .. I understand your request as 'smarter linedrawing' in Query Builder and Schema Designer. We will discuss this, but it is not a small fix!

    in reply to: #26737
    peterlaursen
    Participant

    I am not sure I understand!

    You can rearrange manually of course. But I understand that you are requesting an 'auto-arrange' option?

    I think only user can decide how things should be arranged.

    Anyway can you detail this .. using a few screenshots maybe?

    in reply to: #26733
    peterlaursen
    Participant

    “This clearly is outside MONyog's remit”.

    Why do you think so? SQLite can handle databases in the TB range!

    Also querying the MONyog database can be a little tricky because of the compact Schema design. Most often you will need to use JOINs on derived tables.

    Anyway we will add this to our list and consider after finishing 2.5 release.

    Can you specify more in detail HOW you would like to see the data exported?

    in reply to: #26732
    peterlaursen
    Participant

    I am moving you to the SQLyog category! (this is MONyog!)

    but anyway .. we had a similar request last week actually. Refer to:

    http://code.google.com/p/sqlyog/issues/detail?id=732

    I think we all agree that this is a good idea. But details of implementation will have to be elaborated!

    in reply to: #26731
    peterlaursen
    Participant

    To me this seems only to makes sense when generating the sync script with an empty database as . If is not empty then there is nothing CREATEd for those tables and other objects that were in before sync. Example:

    Source: tables a,b,c

    Target: tables a,b,x

    Further let us say that source.a and target.a are identical in structure and source.b and target.b are different in structure.

    A sync script will (if nothing is deselected):

    ALTER TABLE b, CREATE TABLE c and DROP TABLE x (and nothing do be done with a)

    You propose then that we

    ALTER TABLE b, DROP TABLE IF EXISTS c, CREATE TABLE c and DROP TABLE x (still nothing do be done with a)

    I do not see much use in having that “DROP TABLE IF EXISTS c” statement as c is only one table of 3.

    Can you elaborate?

    in reply to: #26231
    peterlaursen
    Participant

    @LeHHel: Also see this

    http://code.google.com/p/sqlyog/issues/detail?id=606

    In this “also export type to be INSERT/UPDATE and EXPORT. on UPDATE” UPDATE measn REPLACE here? What is “EXPORT. on UPDATE ?

    You should alse be aware that the backup tool of the ENTERPRISE version has more options – among those:

    * complete INSERTs

    * using INSERT DELAYED

    * encoding options

    in reply to: #26489
    peterlaursen
    Participant

    We released approx. 1 hour before I posted!

    in reply to: #25679
    peterlaursen
    Participant

    No decision has been taken. It won't have to be a secret that opinions are divided in our organisation about this!

    A special problem is that SQLyog will need the .ini at startup. If none is found it will create one. It is of course not possible to have the .ini tell where the .ini is! (but there are 'workarounds' of course so this is no excuse really: one idea could be that if .ini is not found in 'AppData' it could next look in a subfolder (inifolder) to installation folder. And same folder would need to be used for log files etc.) before creating a new one in 'AppData'.

    in reply to: #26487
    peterlaursen
    Participant

    Please confirm the fix for this in 6.55.

    We never saw this flicker ourselves, so we would appreciate if you can confirm!

    in reply to: #26484
    peterlaursen
    Participant

    We accept your coding hints. And actually this is not the only place in code where a Window or other GUI object is destroyed and repainted where it is not really required.

    But still it is not reproducable for us. And fixing wihtout reproducing makes it imposible to verify the fix really.

    For the 6.5 tree it is not priority to fix this dues to resources available. I Hope we can review all the code involved in the 7.0 tree.

    in reply to: #26451
    peterlaursen
    Participant

    also this:

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

    .. indicates that *too agressive* InnoDB settings are not always good!

    in reply to: #26463
    peterlaursen
    Participant

    We are in the process of finishing 2.5 beta1 – planned for beginning of next week – and everybody is a little 'hung up'.

    We will decide on priority of this request after this.

    in reply to: #26450
    peterlaursen
    Participant

    Update: slowness with InnoDB reproduced (both in Structure Sync and in OB expansion) with large populated tables

    Please see:

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

    http://code.google.com/p/sqlyog/issues/detail?id=703

Viewing 15 posts - 2,926 through 2,940 (of 7,398 total)