Jump to content

requinix

Administrators
  • Posts

    15,286
  • Joined

  • Last visited

  • Days Won

    435

Posts posted by requinix

  1. "Revolution"? lol. It's another Whatever from the tech world. It's not the first fad used to pump up stock prices, and it won't be the last.

    The current state of glorified autocomplete systems AI contributes just about as much value to the world as The Blockchain does. You remember that whole thing? Wasn't that long ago when The Blockchain was being called a "revolution" too...

    The next Whatever will happen in a few weeks, or months, or years, and every publicly-traded company will jump on that as fast as they can too. (Make sure you're not still holding onto all of your NVDA when that happens.)
    And I'm sure that'll bring its own "revolution" too.

    • Like 1
  2. E_DEPRECATED and E_USER_DEPRECATED are the same thing, with the one difference that the former is used by the engine and the latter is used by trigger_error.

    So the question is in what environments do you care/not care about getting messages about using deprecated features and functionality?

    • Great Answer 1
  3. 2 hours ago, rick645 said:

    Granular level?

    Yes, granular, as in "highly detailed; having many small and distinct parts".

    2 hours ago, rick645 said:

    Why the php tick3.php command does not produce output?

    Because you missed the part in my reply where I said "write a bunch of code". You wrote a very small amount and you're not going to see how ticks work unless you write a lot more.

  4. A tick happens every time the engine does something at a fairly granular level. Like executes a statement, but even lower-level than that.

    The easiest way to understand it is going to be to play with code: set up a ticket handler every 1/2/3/whatever ticks, have it output something, and then write a bunch of code to execute and see what happens.

  5. if ($statu1 = "Online") {
        echo "<font color = green>$status1->nodeValue</font><br>";
    } elseif ($statu1 = "Offline") {
        echo "<font color = red>$status1->nodeValue</font><br>";
    }

    One = does an assignment, which means the above code actually works like

    $statu1 = "Online";
    if ($statu1) {
        echo "<font color = green>$status1->nodeValue</font><br>";

    So naturally, every status will be green.

    Two ==s does equality comparison. (Three ===s is if you want to be pedantic about what it means to be "equal".)

    if ($statu1 == "Online") {
        echo "<font color = green>$status1->nodeValue</font><br>";
    } elseif ($statu1 == "Offline") {
        echo "<font color = red>$status1->nodeValue</font><br>";
    } 

     

    That aside, this is very outdated HTML 4-style markup. You should switch to <span>s and CSS.

  6. I was following along until the "please do this for me" bit at the end.

    REGEXREPLACE + REGEXEXTRACT like that is silly. Not sure where you got it from, but a single REGEXEXTRACT is enough to extract all the <uppercase letter + stuff>s in the cell. Check the documentation/help docs for how to make it match everything instead of just once (which is what it does by default).

    For the regex part, it's currently doing <uppercase letter + lowercase letters> so naturally it will only work with lowercase letters and not with numbers or symbols. If you want to match things that look like <uppercase letter + stuff> then realize that "stuff" is a less precise way of saying "keep going until the next uppercase letter". Or in other words, "anything that isn't uppercase". Because computers need you to be precise if you want them to work a certain way. Excel's regex syntax for "anything that isn't ___" is the same as everybody else does it, so you can check either the docs (which I'm sure include a little bit of regular expression syntax) or virtually any other regex resource to find how to write that.

  7. I'm pretty sure you're encountering https://github.com/mdbtools/mdbtools/issues/312.
    Good news is that it was fixed, bad news is that it was fixed in mdbtools 1.0.1 and Ubuntu 24.04 currently only covers through 1.0.0.

    There might be a third-party PPA out there that has an updated version, but I don't know where to look for one.
    Or you could venture down the path of building it yourself, if you wanted: grab the Ubuntu sources, patch them according to this PR, and build.
    Or for a workaround, I think you'll be safe as long as you're not SELECTing anything that requires 64-bits of data length - meaning a VARCHAR(16777215) is okay but a VARCHAR(16777216) is not.

    • Great Answer 1
  8. That insane number for how much memory it tried to allocate strongly indicates an internal problem. But with both pdo_odbc and the plain odbc extension? Now I'm suspecting MDBTools is the one at fault. Are you using the latest version of that?

    8 hours ago, raphael75 said:

    UPDATE: If I modified the query from "select *..." to "select id, name..." it worked! Do you know what would cause this? Is there any way I can get "select *" to work, or could this be a bug?

    Can you identify exactly which column(s) is causing the problem? What data type is it? Are you able to run SELECT queries on other tables that have a column of the same type?

  9. 5 hours ago, raphael75 said:

    @requinix I have never used gdb before, but I just went through a tutorial on how to use it with php and here is the output. Please let me know if this is what you need:

    Almost there. Do that, then when you get the gdb prompt enter "bt" and it will dump a bunch of numbered lines.

    So far, though, it looks like the problem is in unixODBC, which is surprising as you're already on the current version - that said, it's been a couple years so I'm not sure it's still maintained...

  10. You're reinstalling VS Code for this?

    Either the error isn't fixed like you think, or the thing presenting the error is running from a cached version that somehow hasn't updated. Reloading the window, let alone quitting and restarting, should resolve the latter.

    Maybe some more specific information would be helpful?

×
×
  • 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.