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:
  • 1 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
aquery/aexecute question
Author Message
Shaklaban
Master
**

Posts: 378
Likes Given: 0
Likes Received: 1 in 1 posts
Joined: Mar 2012
Reputation: 8

DOT

Post: #2
RE: aquery/aexecute question
if you index your wb_acc_info table by username column it will run faster. also you need to use:

db.query SELECT email FROM wb_acc_info WHERE username = '<account.name>'

instead of using LIKE.

AEXECUTE and AQUERY only useful for large data processing in background.
(This post was last modified: 07-29-2013 09:16 PM by Shaklaban.)
07-29-2013 09:15 PM
Visit this user's website Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
aquery/aexecute question - Rattlehead - 07-29-2013, 04:06 PM
RE: aquery/aexecute question - Shaklaban - 07-29-2013 09:15 PM
RE: aquery/aexecute question - Rattlehead - 07-30-2013, 03:39 AM

Forum Jump:


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