Re: MySQL and Decimals

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 57845
interpreted = N
texte = Larry Hewitt wrote: > A database with fields defined as DECIMAL, size 10, 2 decimals allows me > to enter or upload information just fine manually. When I try to read > the data using the WEBDNA 6 SQL tags, I return the machine number > equivalent, not the number: ie, 1074266112 instead of 2.0 I suspect that not many people use the DECIMAL field type (usually FLOAT is used). According to the docs DECIMAL values are actually stored in MySQL as strings, which may be part of the problem (though I have no idea why you would get such an odd "machine number" representation like that). One thing you could try is applying various mathematical operations to the field in your select statement: select dec_field+0 as new_dec, ... and see if WebCat deals with it appropriately... 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: > A database with fields defined as DECIMAL, size 10, 2 decimals allows me > to enter or upload information just fine manually. When I try to read > the data using the WEBDNA 6 SQL tags, I return the machine number > equivalent, not the number: ie, 1074266112 instead of 2.0 I suspect that not many people use the DECIMAL field type (usually FLOAT is used). According to the docs DECIMAL values are actually stored in MySQL as strings, which may be part of the problem (though I have no idea why you would get such an odd "machine number" representation like that). One thing you could try is applying various mathematical operations to the field in your select statement: select dec_field+0 as new_dec, ... and see if WebCat deals with it appropriately... 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:

Need a better [elapsedtime] (2000) Duplicate Cart ID (2001) WebCatalog Q & A pages (1997) Emailer choke (1997) Text vs. Math (2000) tabs as delimiters (2004) Individual LineItemChangePassword files would be better ... (1999) shipping confusion (2000) Document Contains No Data! (1997) Bug? (1997) UPPERCASE (1997) Dynamic Image Generation (2000) Mac GUI editors (1997) Re:ListFields and [name] (1997) Can you do this??? and other stuff (1997) Two prices in shoppingcart? (1997) politeness (was searches with dash...) Please Read (2000) all records returned. (1997) WebCatalog Technical Reference (1997) Non WebDNA forms and timed popups... (2002)