It seems the main claimed advantage of dec64 over IEEE 754-2008 decimal64 is in the fast-path zero-exponent case. POWER and RISC-V processors already have hardware support for IEEE 754-2008 decimal floating point numbers, and C# has language support for IEEE 754-2008 decimal floating point.
#AIRTABLE CHANGE PRIMARY KEY UPDATE#
Multi-user planning and documentation via docs is great - I have a shopping list everyone can update and I can see it change real time on the phone in the shop while someone is changing it from their desktop, and it's always up to date. Having said all of the above, I really like Google Docs and it will take some amazing features to make me switch to anything else. I don't know what the alternative might have been - an auto-generated primary key? The app didn't mind importing non-unique values into that first column. I don't have a simple primary key - it's really a composite of. red wines have a red background in that wine type table. I had some conditional formatting set up via Google Docs, which could be nice to have here e.g.
Or maybe there could be an option to convert a text field to a separated linked table. Maybe the dialogue that comes up (suggesting to expand the spreadsheet) could even tell you about that. For example, I could Copy the column and have a some Paste (unique values only) option. Maybe it would be nice to automatically clean that up somehow. 10 different repeated values on 500 rows. The "link to another table" seems interesting, but my data came denormalized so I have a column with e.g. Your app seems sluggish to scroll compared to Google Docs at that size, and the record density seems low (I see 29 records per page vs 50 on Google Docs). I don't know if it would have accepted a spreadsheet. I had to save the file as CSV and import it - or at least that's what I thought, but filepicker seems to support picking from google drive. Here's one use case: i tried importing a 500+ row wine spreadsheet into it (it has columns like type, producer, name, vintage, rating, source etc).
0 kommentar(er)
