Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CONot sure if I understood your workflow. What I don't want is to import the data. The legacy app and the Rails app MUST use the same database at the same time because they run in parallel and we are doing a soft migration from legacy to modern step by step. Working with "execute" and "exec_query" probably would work - but in my opinion exactly that is the kludge. I should use my models to access broken data and let it fix itself by logic implemented in the model.
      singulars
    2. COIt wasn't clear from your original message that the both applications have to share the same database. Or I misunderstood something. If so, then my solution will not work for you, apparently. But I strongly object to having models "fix broken data by logic implemented in them". The logic that your model contain should be about business logic, not some hacks and workarounds for the broken data. Because those kludges will pile up, pollute your business logic and eventually make the code hard to understand. I suggest that you don't go that way :-)
      singulars
    3. COActually, it is contained in the original message: "As the legacy PHP app and this new Rails app need to run in parallel for a few weeks to months, we cannot simply one-time-fix the dates" - but I amended that so it becomes more clear. The logic in my models is designed to be graceful with errors from the old DB (we can very well guess with assumptions in the code what information is missing and insert it on the fly), the same goes for dates (actually a date like offline_at 0000-00-00 16:30 means be offline at the same day as online_at states, the old PHP code handles such cases in code).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload