Re: mySQL numfound
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66687
interpreted = N
texte = Just an FYI. We are going to be doing some testing on a different want to integrate MySQL with DNA. Specifically we currently use MSSQL on most things using the built in ODBC connection from DNA with no issues. However, given that we are now seeing some differences in functionality (numfound not working) we are going to start hitting a MySQL server using the ODBC connection to it and not the native MySQL tags in WebDNA. One distinct advantage should be the 100% compatibility with the 2 backend DB because we control the SQL syntax in the string we send through the ODBC. Also we are not expecting any real loss of performance using this method. I just thought that some of you who are having trouble with MySQL and DNA might consider this as an option. Will let you guys know what we find. Alex On 4/1/06 6:22 PM, "Alex McCombie"
wrote: > Interesting that Numfound works perfectly with MSSQL through an ODBC. We > have been considering setting up a MySQL server and it was thought that we > would have little reworking on our current WebCat/MSSQL code. > > Beginning to second guess that. > AJM > > > > > On 4/1/06 5:17 PM, "brian@orderbywire.com" wrote: > >> Thanks adam. >> I think I will go with the double search. I would be interested to see how >> you put together that paging function though. >> >> thanks >> >> >> Brian Boegershausen >> Endeavotech Advanced Business Solutions LLC. >> http://www.endeavotech.com >> brian@endeavotech.com >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Adam >> O'Connor >> Sent: Saturday, April 01, 2006 11:48 AM >> To: WebDNA Talk >> Subject: Re: mySQL numfound >> >> Brian, >> >> Sorry was out of town, there are a couple of methods to retrieve the >> numfound via MySQL - however they both require more than one search - that >> is if you are limiting the main recordset. 1) You can either do an >> un-restricted search and return all rows thus get a numfound value or 2) Use >> an alias within your SQL syntax using MySQL's count(*) function. >> >> If you need more assistance, I can send you a paging function that resembles >> webcats. My best advice is to study PHP when developing with MySQL & >> webcat. Whenever you get held up from webcat's limited SQL functionality, >> just look at how to accomplish the task via PHP, then model this function >> via webcat. Hope this helps. >> >> >> >> >> >> >> Donovan Brooke wrote: >>> brian@orderbywire.com wrote: >>> >>>> Has anyone come across a solutions to display the [numfound] in a >>>> mysql search result? >>>> >>>> The [numfound] tag only shows the LIMIT in the mysql search content. >>>> If you >>>> put a numfound tag in a WebDNA search, it shows the number found in >>>> the DB, not the MAX in the search context. >>>> >>>> To properly set up my PREVIOUS & NEXT buttons, I need the know the >>>> total number of records returned in the search. >>>> The only thing I can think to do is write the search twice on the >>>> page and not set the LIMIT. >>>> >>>> Any thoughts would be appreciated. >>>> >>>> Thanks >>>> Brian >>> >>> Brian, >>> could you post your code. If you are putting a limit on your select >>> statement, yea, numfound would return your limit. I'm a newb at SQL >>> but I would think you could execute an SQL native "numfound" >>> and then reference that. Off the top of my head, Isn't it something >>> like foundcount? >>> >>> I'm sure somone will have better info for you but it would help us if >>> you posted your code. >>> >>> Donovan >>> >>> >>> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ -- Alex J McCombie Adventure Skies Interactive (ASI) Alex@Adventureskies.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Just an FYI. We are going to be doing some testing on a different want to integrate MySQL with DNA. Specifically we currently use MSSQL on most things using the built in ODBC connection from DNA with no issues. However, given that we are now seeing some differences in functionality (numfound not working) we are going to start hitting a MySQL server using the ODBC connection to it and not the native MySQL tags in WebDNA. One distinct advantage should be the 100% compatibility with the 2 backend DB because we control the SQL syntax in the string we send through the ODBC. Also we are not expecting any real loss of performance using this method. I just thought that some of you who are having trouble with MySQL and DNA might consider this as an option. Will let you guys know what we find. Alex On 4/1/06 6:22 PM, "Alex McCombie" wrote: > Interesting that Numfound works perfectly with MSSQL through an ODBC. We > have been considering setting up a MySQL server and it was thought that we > would have little reworking on our current WebCat/MSSQL code. > > Beginning to second guess that. > AJM > > > > > On 4/1/06 5:17 PM, "brian@orderbywire.com" wrote: > >> Thanks adam. >> I think I will go with the double search. I would be interested to see how >> you put together that paging function though. >> >> thanks >> >> >> Brian Boegershausen >> Endeavotech Advanced Business Solutions LLC. >> http://www.endeavotech.com >> brian@endeavotech.com >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Adam >> O'Connor >> Sent: Saturday, April 01, 2006 11:48 AM >> To: WebDNA Talk >> Subject: Re: mySQL numfound >> >> Brian, >> >> Sorry was out of town, there are a couple of methods to retrieve the >> numfound via MySQL - however they both require more than one search - that >> is if you are limiting the main recordset. 1) You can either do an >> un-restricted search and return all rows thus get a numfound value or 2) Use >> an alias within your SQL syntax using MySQL's count(*) function. >> >> If you need more assistance, I can send you a paging function that resembles >> webcats. My best advice is to study PHP when developing with MySQL & >> webcat. Whenever you get held up from webcat's limited SQL functionality, >> just look at how to accomplish the task via PHP, then model this function >> via webcat. Hope this helps. >> >> >> >> >> >> >> Donovan Brooke wrote: >>> brian@orderbywire.com wrote: >>> >>>> Has anyone come across a solutions to display the [numfound] in a >>>> mysql search result? >>>> >>>> The [numfound] tag only shows the LIMIT in the mysql search content. >>>> If you >>>> put a numfound tag in a WebDNA search, it shows the number found in >>>> the DB, not the MAX in the search context. >>>> >>>> To properly set up my PREVIOUS & NEXT buttons, I need the know the >>>> total number of records returned in the search. >>>> The only thing I can think to do is write the search twice on the >>>> page and not set the LIMIT. >>>> >>>> Any thoughts would be appreciated. >>>> >>>> Thanks >>>> Brian >>> >>> Brian, >>> could you post your code. If you are putting a limit on your select >>> statement, yea, numfound would return your limit. I'm a newb at SQL >>> but I would think you could execute an SQL native "numfound" >>> and then reference that. Off the top of my head, Isn't it something >>> like foundcount? >>> >>> I'm sure somone will have better info for you but it would help us if >>> you posted your code. >>> >>> Donovan >>> >>> >>> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ -- Alex J McCombie Adventure Skies Interactive (ASI) Alex@Adventureskies.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Alex McCombie
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Processing stops (2006)
TCPConnect misbehavin' for me. (2000)
Problem (1997)
[sendmail] problem getting silly now =\ (2000)
Separate SSL Server (1997)
Need relative path explanation (1997)
Re:2nd WebCatalog2 Feature Request (1996)
WebDNA Codes in Secure Mode (1997)
2.0 Info (1997)
International Orders (1998)
browser info.txt and SSL (1997)
Shopping carts and reloading pages (1997)
[WebDNA] WebSite Examples (2008)
E-mail/Invoice (1998)
RE: Last desperate attempt (1998)
Unexpected comparison behavior change in 4.5.1 (2003)
WebCat2b15MacPlugin - showing [math] (1997)
Searching multiple fields (1997)
required fields (1998)
CC Processing (2001)