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

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: Segmentation Fault using SJA on Linux 9.0 #16690
    JasonPotter
    Member

    Hi There,

    It has now been a couple of months since this error was raised, is there a fix?

    Regards

    Jason

    in reply to: Capturing sja output #16069
    JasonPotter
    Member

    Hi All,

    Does anyone else get the same problem as I have above or do you think it is an environment setup issue?

    Cheers

    Jason

    in reply to: sja Timeout issue #15988
    JasonPotter
    Member

    Hi There,

    Is there a location where we can see what the dev team is currently working on. ie. a feature list?

    Cheers

    Jason

    in reply to: Remote Database update #15862
    JasonPotter
    Member

    Hi Guys,

    just saw another post that stated sja can handle multiple keys. Now just have to confirm it can handle a column being auto inc at one end and not at the other.

    Cheers

    Jason

    in reply to: Remote Database update #15861
    JasonPotter
    Member

    Hi Robmann,

    To do this I would have a seperate table with has an auto inc field in it. Before I do an insert in the main table I do an insert into that table first. Get the resulting id apend my site prefix and use this as my primary key in the main table.

    Another way which I just thought of but not sure it will work is as follows:

    Create a multiple column primary key on the source with one of the columns being an auto inc the other has a default value of the site prefix.

    On the target you have the same structure but no auto inc column.

    If sja can handle this the sync will work not a problem.

    Cheers

    Jason

    in reply to: Remote Database update #15859
    JasonPotter
    Member

    Thanks for the response.

    Though I thought sja will delete the enteries in the target if they are not in the source or is this a configurable feature? Hence when you do the first sync the target will become exactly like Source1 and then after the second sync the target will exactly be like Source2, hence wiping out the data entered into the target from the first sync.

    Also what would the issues be if any, if Source1 and Source2 tried to do their syncs at the same time. In my case Source1 and Source2 are not always connected to the net and initiate their on connections. I would prefer not to have to specify connect times as these Source db's will connect to the net via GPRS and I am not always going to have a signal. So if I have a signal and can make a net connection via gprs I want to do the sync straight away. So there is a chance of 2 sync's running at the same time.

    I look forward to your response on both points.

    Cheers

    Jason

    in reply to: Remote Database update #15857
    JasonPotter
    Member

    Hi Guys,

    Have a similar situation and wanted to know if sja could handle this one.

    I have multiple remote databases, which I will represent as Source1 and Source2 below. These have to sync back to a master db once a day with their data. These remote db's do not need to be updated. Eg Source1 does not have to contain Source2 info. Below is a visual representation of what I need too do.

    source1:

    =========

    S1_1 OnlineSQLyog

    S1_2 SQLyog

    S1_3 Ritesh

    source2:

    =========

    S2_1 DiffSQLyog

    S2_2 SQLyog

    S2_3 Ritesh

    Master:

    ========

    S1_1 OnlineSQLyog

    S2_1 DiffSQLyog

    After sync is run the only table that is updated is the Master.

    Master:

    ==========

    S1_1 OnlineSQLyog

    S2_1 DiffSQLyog

    S1_2 SQLyog

    S1_3 Ritesh

    S2_2 SQLyog

    S2_3 Ritesh

    I look forward to your response.

    Cheers

    Jason

    in reply to: Two say synchronization #15303
    JasonPotter
    Member

    Ritesh,

    When do you see 3.7 being released?

    Cheers

    Jason

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