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

Forum Replies Created

Viewing 15 posts - 2,731 through 2,745 (of 7,398 total)
  • Author
    Posts
  • in reply to: #27227
    peterlaursen
    Participant

    “Also I have tried to access the tunneling URL from a browser, and get an error500”. This will have to be solved first!

    1) Can you access a very simply PHP file in same folder?

    2) Please try to create an empty folder and copy the tunneller there. Turn off global directives for that folder (in Apache you copy an empty .htaccess there) . Now try connect again.

    3) Did you try the server support?

    in reply to: #27224
    peterlaursen
    Participant

    You already created 2 tickets about the same! Why now this? One report per problem please. We cannot discuss the same thing 3 different places. This will only slow dowd the process actually, because it is wasting our resources! Also it is very bad netiquette!

    Please decide if you want to continue here or in one of the tickets! BUT ONE PLACE ONLY!

    in reply to: #27223
    peterlaursen
    Participant

    We are in the process of making dialogues resizable. Refer to changlelogs for the 7.1 betas!

    The SJA wizard will also be, but this one in particular is little complicated, because every 'step' of the wizard has different kind of objects in it – that should also be resizable ideally. 7.1 will ship with the current wizard design.

    in reply to: #27214
    peterlaursen
    Participant

    You have 4 identical rows in the table. I repeat: *identical*. So the WHERE clause in the UPDATE statement sent by SQLyog will be satisfied by all 4 rows.

    This FAQ explains:

    http://webyog.com/faq/content/28/70/en/i-o…tabase-why.html

    .. the point is that SQLyog communicates with the server using SQL (because this is simply how you communicate with a SQL-server!). In SQL-databases tables are supposed to have a Primary Key basically! Duplicate rows in SQL databases is a mess! You should ensure that it does not occur!

    Most simple solution: after import add a auto-increment Primary Key column to the table (from table context menu .. alter table)

    We have added to our issue tracker an option for user to define a LIMIT clause (like “UPDATE .. SET .. WHERE .. LIMIT 1”) for the UPDATE (or DELETE) statement in this situation. But this is not priority. Because the basic problem is the user's table design.

    in reply to: #27213
    peterlaursen
    Participant

    1) The link is a discussion about Data Sync. With Data Sync 'echoing to a file' is an option from version 7.0.

    2) We also had request to 'spool' HISTORY to a file. This is listed in our TODO but not in development currently.

    in reply to: #27211
    peterlaursen
    Participant

    OK .. we will discuss next week!

    Are you aware that double-clicking on such object will paste the name into the editor?

    in reply to: #27204
    peterlaursen
    Participant

    The culprit is this “* Selling software that requires customers to install MySQL themselves on their own machines.” I admit that this surprises me actually. I will ask somebody else to comment on that. In my understanding this is not compliant with GPL – but I may be wrong!

    We (webyog) have no commercial license for the MySQL server from MySQL/Sun! But our program also do not *require our customers to install MySQL themselves on their own machines*. Our programs will work BOTH with MySQL installations on local and remote machines. So we do not *require* any local installation!

    in reply to: #27209
    peterlaursen
    Participant

    This is now fixed in trunk. Fix will be included in next release!

    in reply to: #27208
    peterlaursen
    Participant

    Issue confirmed. Seems that proxy authentication was broken in recent versions (the issue is in the wizard, not in SJA).

    We are analyzing and hope to fix in next release.

    in reply to: #26454
    peterlaursen
    Participant

    “So either disk, or windows genuine advantage failing seemed to really hammer performance of database synchronization tool.”

    It must absolutely be an issue with the disk performance then!

    in reply to: #27206
    peterlaursen
    Participant

    Please

    * attatch the jobfile (you can 'fake' hosts, passwords etc. if you want)

    * attach a structure-only dump of the database (or better from both databases if servers are different versions)

    * tell the server versions (if the dumps don't).

    You may create a ticket if you want privacy!

    Also tell: was the jobfile created with the GUI wizard?

    in reply to: #27205
    peterlaursen
    Participant

    This is by design! The idea of a Primary Key is that it is a unique identification of rows! Two rows on different servers with the same PK-value are considered identical (every SQL database tool would!)

    To avoid this happening you will need to define the PK so that the PK-values created on either server are always different.

    There are (at least) two ways to do this:

    1) You can define server variables auto_increment_increment and auto_increment_offset in the server configurations so that an INTEGER PK will be 1,3,5,7 etc of one host and 2,4,6,8 etc on the other host for instance. This will only work with recent servers and you will of course need to have access to server configuration

    2) You can add a column that is constant – but different – on either host. Next re-define the PK to include that column.

    But note that with both solutions you will need to DELETE rows on both hosts should you wnat to delete. Because if you only delete on one it will be re-created on the other after sync.

    in reply to: #27165
    peterlaursen
    Participant

    Wine is supposed to be a port of the Win-32 API for Unix. The Win-32 API is a low-level collections of classes, functions etc. used to address/manage the basic functionalities of the Windows operating system

    But the functions etc. in Wine sometimes work slightly different than the original Win-32 API. A common issue is that variables are not initialized exactly the same way. This you could call a bug in Wine – but as it exists we will have to code around it (sometimes however it will help if you update Wine!)!

    Here we used functions to manage a tree-view GUI element .. and different from how we used those in versions before 7.0. There was such issue where the exact behaviour of the original Win-32 API and Wine was not quite the same.

    in reply to: #27199
    peterlaursen
    Participant

    No, it is *not a bug* – this was removed.

    in reply to: #27202
    peterlaursen
    Participant

    The short answer is that MySQL server is GPL-licensed. If you distribute a program that is not GPL-licensed you cannot distribute the MySQL server with it without a(n commercial) agreement with MySQL/Sun. But your users/customers can download and install the MySQL server themselves without problems! There are *TENS OF THOUSANDS* of individuals and companies that distribute software designed for MySQL. 99.9% distribute without the server. Users can easily download and install the server themselves.

    However, if you want to distribute an application and bundle the MySQL server, I would (even if it is an Open Source program) recommend that you contact MySQL/Sun. There are some pitfalls with 'interaction' between different different GPL versions and other Open Source licenses (Mozilla license, BSD license etc. etc.).

Viewing 15 posts - 2,731 through 2,745 (of 7,398 total)