Viewing 15 posts - 61 through 75 (of 223 total)
Opinion noted... However, I can more easily do things with DATETIME that can only be dreamed of with DATETIME2. Even Microsoft realized their mistake but, instead of fixing it,...
January 16, 2020 at 8:07 pm
Possibly, but then again, we all know how much accountants love guesswork, right 😀
Anyway, I could easily dig up examples from the EU where the conversion rates between the EURO...
January 16, 2020 at 4:02 pm
I think there are accounting standads that say 4 d.p. should be used for money calculations.
Well, that would depend on your country of operation, wouldn't it?
January 16, 2020 at 3:29 pm
Actually, MONEY is useful if only for documentation purposes. You could use decimal but why would you want to? Being an integer makes the type faster than decimal.
DATETIME does...
January 16, 2020 at 3:22 pm
Yes, because MONEY is a precise data type with 4 decimal places. It's implemented as a 64-bit integer, scaled down by 10000. That and DATETIME must be the two lamest...
January 16, 2020 at 3:06 pm
I think the extra decimal digit is because if you multiply a number with 2 decimal places by a number with 1 decimal place, the result can have 3...
January 16, 2020 at 2:44 pm
Yes, a strange result. Try this:
DECLARE @tmp1 FLOAT = 0.289;
SELECT CONVERT(decimal(38,36),ROUND(@tmp1, 2)*100),
CONVERT(decimal(38,36),ROUND(@tmp1, 2))*100
Well, that's no more strange than any...
January 16, 2020 at 2:29 pm
Well, 29 would have been too easy, and the title of the QOTD hinted at the result not being quite the obvious. Casting to INT always truncates decimals, so it...
January 16, 2020 at 10:11 am
Good one!
The problem is that casting to int always removes any decimals, and with the example, 0.289 is actually stored as a value which, when converted with the maximum number...
January 16, 2020 at 8:49 am
Option 1 works only if you replace the {} with [] as follows:
df.columns = ['BillMonth', 'InvoiceAmount']
True, dat! So, we're down to the missing alternative of "None", I suppose...
December 18, 2019 at 9:06 pm
Option 1 may well work, but in this instance, it's renaming the wrong field so is wrong for the question posted.
(I know, I'm being really picky now).
I really don't...
December 18, 2019 at 11:56 am
Option one won't work as it's renaming the wrong field.
Option one should work, shouldn't it, since it sets the name of all the columns, but uses the old name...
December 18, 2019 at 11:37 am
I thought I wouldn't touch this question until it's been reviewed, but I couldn't resist.
Clearly, option 3 wouldn't work, since the original column name is "BillingAmount", and not "BillAmount". In...
December 18, 2019 at 8:30 am
I'll defer answering until Steve has sorted this one out.
November 27, 2019 at 10:43 am
Well, unfortunately, the documentation is a bit off. The bit about the session settings is correct, which matches what I wrote.
The bit about the database settings is incorrect. The correct...
November 25, 2019 at 9:34 am
Viewing 15 posts - 61 through 75 (of 223 total)