Jump to content

requinix

Administrators
  • Content Count

    13,476
  • Joined

  • Last visited

  • Days Won

    322

requinix last won the day on June 23

requinix had the most liked content!

Community Reputation

1,005 Excellent

5 Followers

About requinix

  • Rank
    Abandoned Administrator

Profile Information

  • Gender
    Not Telling
  • Location
    America/Los_Angeles

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you only care about checking individual dates that are available, that's fairly easy: store the unavailability dates as rows of start and end dates, then search for rows based on whether the day is between them. If you care about checking date ranges then it's a bit trickier, but still not as complicated as it might sound: a conflict is any row where the desired start date is before the unavailable end date, and the desired end date is after the unavailable start date.
  2. In general, try to use z-index as little as possible. How is overflow configured on the parent row? If it isn't allowed then the arrow will clip when you try to position it partly out of bounds.
  3. A screenshot isn't the most helpful thing. Got a link to the webpage?
  4. That comes from $sql2 = " SELECT order_id FROM ordered_items GROUP BY order_id WHERE order_id = '".$row[order_id]."' "; this query. So if this query isn't working then your next step is to learn more about $row.
  5. It probably doesn't work because your "button" is actually a link. But I don't actually know what "output" you're trying to get...
  6. Well, you could do it... you know... recursively. As in you do one query to find the next step's relations, then another query for the next, and another for the next, until you've gone as far as you want (or you run out of relations). Remember not to check IDs you've already seen before. Depending on your database server, you may be able to write a recursive SQL query using CTEs...
  7. Don't use the version from FlatPak: it's unofficial and apparently buggy. Install VS Code from an official source.
  8. Keep track of the previous row. When the current row's year (or whatever you want to measure by) changes then you stick an ID on the table row.
  9. Probably? It's a package manager. See if you have it installed, and if so if it thinks VS Code was installed through it.
  10. Did you install the "FlatPak" version of VS Code?
  11. You need to stop saying "group by" and start describing what you want to do.
  12. That does not help to explain why you're doing this. I'm asking because this query INSERT INTO invoice_price (order_id) SELECT order_id FROM ordered_items GROUP BY order_id WHERE order_id = '$order_id' doesn't make any sense: you take the $order_id that you already know, search for it in the ordered_items table, and then insert those results into invoice_price? Why aren't you inserting the $order_id value directly just like you did with ordered_items?
  13. There could also be a bug with annotation support. It really should not be that inconsistent - unless there's some kind of technical limitation. Probably.
  14. PHP does not parse /** */ docblocks. That's Doctrine/Symfony (I forget which one technically does the annotation support). But code doesn't behave randomly so there must be some difference between the situation that works and the one that does not. Either way, the answer is the same: don't import stuff you don't need, do import stuff you do need.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.