Re: MySQL and Decimals

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 57851
interpreted = N
texte = Larry Hewitt wrote: > [SQLExecute conn_ref=conn1&result_var=1] > SELECT * FROM QUICKFACTS ORDER by ID; > [/SQLExecute] FWIW, this is sloppy code; you should always specify the fieldnames in your SQL query, even if you intend to use all of them. The reason for that is performance; if you use "SELECT *" then the query optimizer has to lookup the fields in the system table, then check for any applicable indexes, and only then perform the actual query. Since WebDNA does not support cursors, every single page will require all of the above steps. If you can cut out the system table query, you can save precious CPU cycles for more important use. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- 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:

    
  1. Re: MySQL and Decimals ( "Sal" 2004)
  2. Re: MySQL and Decimals ( Larry Hewitt 2004)
  3. Re: MySQL and Decimals ( John Peacock 2004)
  4. Re: MySQL and Decimals ( Larry Hewitt 2004)
  5. Re: MySQL and Decimals ( Larry Hewitt 2004)
  6. Re: MySQL and Decimals ( Larry Hewitt 2004)
  7. Re: MySQL and Decimals ( John Peacock 2004)
  8. MySQL and Decimals ( Larry Hewitt 2004)
Larry Hewitt wrote: > [SQLExecute conn_ref=conn1&result_var=1] > SELECT * FROM QUICKFACTS ORDER by ID; > [/SQLExecute] FWIW, this is sloppy code; you should always specify the fieldnames in your SQL query, even if you intend to use all of them. The reason for that is performance; if you use "SELECT *" then the query optimizer has to lookup the fields in the system table, then check for any applicable indexes, and only then perform the actual query. Since WebDNA does not support cursors, every single page will require all of the above steps. If you can cut out the system table query, you can save precious CPU cycles for more important use. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- 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/ John Peacock

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:

Professional WebDNA Hosting Solutions (2005) [WebDNA] How do we tell what's misconfigured? Or which WebDNA 7 version to use? (2011) WCS Newbie question (1997) two unique banners on one page (1997) Date search - yes or no (1997) Replace context problem ... (1997) passing search criteria (1997) Error Log.db --however (1997) Changes to the List (1997) RE: Problems with shopping cart (1997) problems with 2 tags (1997) Extended [ConvertChars] (1997) WebCat2_Mac RETURNs in .db (1997) Mac 4.0b2 Installer Problems (2000) Variables for chat (1997) Cart Number Propagation (1997) [searchString] (1997) Tax on Shipping question (1998) Add to cart issue (2007) WebDNA 5.1 is now available! (2003)