in reply to Re^3: checking mysql rows continuously
in thread checking mysql rows continuously

This node falls below the community's threshold of quality. You may see it by logging in.

Replies are listed 'Best First'.
Re^5: checking mysql rows continuously
by marto (Cardinal) on Dec 08, 2020 at 16:03 UTC
    A reply falls below the community's threshold of quality. You may see it by logging in.
Re^5: checking mysql rows continuously
by stevieb (Canon) on Dec 08, 2020 at 17:20 UTC
    "you can't blame IBM for using fetchrow"

    Yes, you most certainly can. IBM has a track record of mucking with things that didn't need mucking with.

    The authoritative source for the use of a Perl distribution is the author's documentation, not a completely unaffiliated company.

    I have had my software modified by a company in the past without any mention of the change, while leaving my contact information in the troubleshooting section. It was infuriating when I received a large number of email complaints that "your software doesn't work!".

    Regardless of what it is, you're doing something wrong as your code isn't doing what you want, so leave IBM out of it, and refer to the proper documentation. That's your best bet to get back on track.

    The authoritative methods you're looking for are:

    fetchrow_arrayref() # fetch a single row, put it into an array referen +ce fetchrow_hashref() # fetch a single row, put it into a hash reference fetchall_arrayref() # fetch all rows into an aref of arefs fetchall_hashref() # fetch all rows into an href of hrefs

      ok

Re^5: checking mysql rows continuously
by Anonymous Monk on Dec 08, 2020 at 16:15 UTC
    so you can't blam ibm of using fetchrow

    yes you can