The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Strange MySQL Behavior
Author Message
n1ghtwish
Apprentice
*

Posts: 40
Likes Given: 0
Likes Received: 28 in 8 posts
Joined: Jan 2016
Reputation: 0



Post: #5
RE: Strange MySQL Behavior
(02-12-2016 03:24 AM)Ben Wrote:  Since the error happens after the first row... It's possible the there is some data in the next row that sphere can't handle.

Ben, thanks for the reply and that's a valid assumption. However, answer the following question regarding that...

why would the same debug message show up when I query the table with only 1 row, without the loop? simply a "db.query etc...." single line of code.

At this time, I have narrowed down the issue to ONLY MySQL queries (does not happen with execute). Also, the error only seems to appear while using the * operator inside the query... if I rewrite the function as follows, I do not get the debug errors at all and the command executes properly:

Code:
local.col = acctname
local.table = accounts
db.query "select <local.col> from <local.table>"
serv.log @Test: Querying column "<local.col>"
serv.log @Test: <eval <db.row.numrows>> rows returned.

for X 0 <eval <db.row.numrows> -1>
    serv.log @Test: Row # <eval <dlocal.x> + 1> account name is <db.row.<dlocal.x>.acctname>
endfor�
02-15-2016 04:23 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
Strange MySQL Behavior - n1ghtwish - 02-08-2016, 05:19 PM
RE: Strange MySQL Behavior - darksun84 - 02-09-2016, 07:20 AM
RE: Strange MySQL Behavior - n1ghtwish - 02-09-2016, 02:25 PM
RE: Strange MySQL Behavior - Ben - 02-12-2016, 03:24 AM
RE: Strange MySQL Behavior - n1ghtwish - 02-15-2016 04:23 AM
RE: Strange MySQL Behavior - n1ghtwish - 02-15-2016, 04:01 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)