[DiscordArchive] The 4 float, were they signed too?
[DiscordArchive] The 4 float, were they signed too?
Archived author: stevej • Posted: 2021-01-16T17:49:00.121000+00:00
Original source
The 4 float, were they signed too?
Archived author: stevej • Posted: 2021-01-16T17:50:10.948000+00:00
Original source
The problem, is that at least in the SQL, I have noticed, that when it is signed, it does not specify it, it only does it in case of being unsigned.
Archived author: stevej • Posted: 2021-01-16T18:02:12.280000+00:00
Original source
What do you think about it? When it is not clear, should we add that it is signed? <@!109652764488892416> <@456226577798135808>
Archived author: stevej • Posted: 2021-01-16T18:02:50.870000+00:00
Original source
```
| [target_x][10] | float | signed | | NO | 0 | | |
| [target_y][10] | float | signed | | NO | 0 | | |
| [target_z][10] | float | signed | | NO | 0 | | |
| [target_o][10] | float | signed | | NO | 0 | | |
| [comment][11] | text | | | NO | | | Event Comment |
```
Archived author: Deleted User • Posted: 2021-01-16T18:06:48.902000+00:00
Original source
I think we can avoid it, signed is default type of number I think
Archived author: stevej • Posted: 2021-01-16T18:10:39.526000+00:00
Original source
The thing is that sometimes we clarify them, for example, in the `entryorguid` of `smart_scripts` we clarify it. Because it can have positive values as negative, but if you look at SQL, it only makes mention, when they are only positive. I am mostly to know, because if not, from now on, every time I see an (integer, float) that is not `unsigned`, I automatically `signed` it.
Archived author: stevej • Posted: 2021-01-16T18:11:10.929000+00:00
Original source
It really doesn't cost me anything to add it.