On 2022-07-29 11:34, Mark Fletcher via groups.io wrote:

For a numerical type, should there also be a precision field? That is, you would be able to specify how many digits after the decimal (including 0)?

I think it should (with a default of 0) so it can accommodate fractional numerical values and sort them correctly, otherwise the same problem could happen, I guess depending on how that db software works in that regard.  Plus there's the question of what would happen if it doesn't and someone tries to enter a fractional number in a numeric field type.

As to how many decimal digits to allow, some graphics apps (like Coreldraw for example) allow up to 6 digits for drawing precision, so for some user support groups (like the Coreldraw User group here on GIO or maybe other science/engineering-type groups) having only 3 digits allowed may not be as useful.

Cheers,
Christos

On Fri, Jul 29, 2022 at 06:42 PM, Christos Psarras wrote:

As to how many decimal digits to allow,

Would a floating point definition be useful?

Regards
Andy

On Fri, Jul 29, 2022 at 06:48 PM, Mark Fletcher wrote:

I'm thinking of also including a prefix character that you could select, like dollar sign, pound sign, euro sign. What other characters should be an option?

In addition to currency prefix symbols, is there any desire for weights and measures suffixes such as Kg, g, L, ml, cc, cm, m, in, ft, yds, hrs, min, sec etc?

Regards
Andy

When I add this, I'm thinking of also including a prefix character that you could select, like dollar sign, pound sign, euro sign. What other characters should be an option?

 
I'd suggest to also include the tilde ~ (or ≈) so a number can be denoted as being an approximation.  More possible characters could be some of the math symbols/operators, % ≡ > ≥  < ≤ ≠ etc.

Cheers,
Christos

On Fri, Jul 29, 2022 at 01:51 PM, Andy Wedge wrote:

In addition to currency prefix symbols, is there any desire for weights and measures suffixes such as Kg, g, L, ml, cc, cm, m, in, ft, yds, hrs, min, sec etc?

I can see wanting both prefix and suffix, but I doubt that I'd need them.  I would specify the unit as part of the column name being used - Weight(lb), Height(feet), or Cost($).  Of course, there will be those that don't quite see it.  Right now, I have one that says Phone(xxx-xxx-xxx) and people still use other formats like (915) 325-1234.

Duane

This is one of those suggestions where the best can rapidly become the enemy of the good.

My view is that what is important is to be able to say 'it's number, treat it as such': going further you have all sorts of complications over those settings loosely grouped as 'locale' (as to what the decimal point indicator is, currency symbol, etc., etc.) - if Mark can easily find and incorporate routines to handle all these it would be good, otherwise forget them and just have a simple 'it's a number' with any explanation in column headings. 

Jeremy
,

I'd suggest it be blank, since 0 actually may mean something in some use cases. And like any field, I'd like to see it editable and clearable.

On Tue, Aug 2, 2022 at 11:27 PM, Mark Fletcher wrote:

For the number field, is it important to have it be blank until it is set to a specific number

I would define it as a null value rather than blank which could be interpreted by some to mean a space character.

Regards
Andy

On Wed, Aug 3, 2022 at 03:38 PM, Mark Fletcher wrote:

If you convert an existing Single Line Text column to a Number, it will automatically convert any existing numbers properly.

Oops, didn't work.  Luckily, changing it back to Single Line Text brought the numbers back.

Duane