re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
sant0ro
Yes, i will rewrite the whole code, (at least how much code i can rewrite). I preffer that, i know is a big work, more than create from scratch. But if you see the Github Repository, will see that the code is starting to being better.
If it is more work than create from scratch, why wouldn't you then just create from scratch? Besides that, there's more 'dislikes' in the whole Azure shit than just the code. I only have to say the word database. The database design isn't the best either. If you were to change that, you had to change up even more on the emulator.
Yupi! - C# 6 Rosylin - MySQL / Based on old Azure Emulator
Quote:
Originally Posted by
Glaceon
If it is more work than create from scratch, why wouldn't you then just create from scratch? Besides that, there's more 'dislikes' in the whole Azure shit than just the code. I only have to say the word database. The database design isn't the best either. If you were to change that, you had to change up even more on the emulator.
You're right. Im redesigning the database.
Also Glaceon, your normalization's recommendations are right. If you check the change log and changes in github will see.
Sent from my iPad using Tapatalk
Sent from my iPad using Tapatalk
Yupi! - C# 6 Rosylin - MySQL / Based on old Azure Emulator
Also Glaceon, your normalization's recommendations are right. If you check the change log and changes in github will see.
Sent from my iPad using Tapatalk
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
sant0ro
Also Glaceon, your normalization's recommendations are right. If you check the change log and changes in github will see.
Sent from my iPad using Tapatalk
About the room owner was just one thing. Haven't checked the whole database for bad typing, as I have seen a lot of times in the past the database designer used an integer for a number that should never be below 0. For that you should use an unsigned integer. But that only applies when you're 100% sure it cannot go below 0. (For example, coins, all primary keys, duckets etc etc...)
But that's all up to you to figure out :-)
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
Glaceon
About the room owner was just one thing. Haven't checked the whole database for bad typing, as I have seen a lot of times in the past the database designer used an integer for a number that should never be below 0. For that you should use an unsigned integer. But that only applies when you're 100% sure it cannot go below 0. (For example, coins, all primary keys, duckets etc etc...)
But that's all up to you to figure out :-)
I already did that. I know all these things, Glaceon. I only didn't finished the database normalisation.
Sent from my iPad using Tapatalk
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
@sant0ro when u start to update the github with updates agian?
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Hi, great work! Do you have a SWF pack for Yupi Emulator please ?:w00t:
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Any SWF Pack for this? Azure's one isnt working good (catalogue messed up).
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
Multify
Any SWF Pack for this? Azure's one isnt working good (catalogue messed up).
Go to Yupi\Build\Variables\Cache and delete FurniDataCache.xml (worked for me)
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
Glaceon
Haven't checked the whole database for bad typing, as I have seen a lot of times in the past the database designer used an integer for a number that should never be below 0. For that you should use an unsigned integer. But that only applies when you're 100% sure it cannot go below 0. (For example, coins, all primary keys, duckets etc etc...)
Well it's not like you're going to have max integer coins inside your purse. There is no need to use an unsigned integer for coins, tickets and all values that require math where something might be subtracted. Because the result might be below zero. That's why youtube broke on 2147483647 views and not on 4294967295 views. When subtraction is involved, then stick with signed values.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
CodeDragon
Well it's not like you're going to have max integer coins inside your purse. There is no need to use an unsigned integer for coins, tickets and all values that require math where something might be subtracted. Because the result might be below zero. That's why youtube broke on 2147483647 views and not on 4294967295 views. When subtraction is involved, then stick with signed values.
To add on that, the client uses signed integers too, so there is not reason to use unsigned server side.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
Joopie
To add on that, the client uses signed integers too, so there is not reason to use unsigned server side.
I still wondering how they deal with more furniture like that. I'm certain there are more than 2^31-1 furniture around. They have over 250 million accounts registered.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
CodeDragon
Well it's not like you're going to have max integer coins inside your purse. There is no need to use an unsigned integer for coins, tickets and all values that require math where something might be subtracted. Because the result might be below zero. That's why youtube broke on 2147483647 views and not on 4294967295 views. When subtraction is involved, then stick with signed values.
Then you're better of using something different than an int, maybe a smallint or something. But in my eyes (and this is and stays my opinion) it's better to use an unsigned value for something that won't come below 0. Also, "that's why youtube broke on .... views", if you do things correctly (which you should) you wouldn't get any bugs when using unsigned int. But I'm saying before 900000 hate reactions, this is just my opinion.
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
Glaceon
Then you're better of using something different than an int, maybe a smallint or something. But in my eyes (and this is and stays my opinion) it's better to use an unsigned value for something that won't come below 0. Also, "that's why youtube broke on .... views", if you do things correctly (which you should) you wouldn't get any bugs when using unsigned int. But I'm saying before 900000 hate reactions, this is just my opinion.
Things will also break when you hit 2^31+ just because client side it will be a negative number.
Signed or unsigned, it doesn't matter..
Signed: check if it's not below zero.
Unsigned check if it's not above 2^31-1
Both cases have advantages and disadvantaged.
Don't see this as a hate but in this case we are limited to the client which uses signed and because of that is there no real advantages of using unsigned over signed ints
re: Yupi Emulator [C# 6/NHibernate/Post-Shuffle]
Quote:
Originally Posted by
Joopie
Things will also break when you hit 2^31+ just because client side it will be a negative number.
Signed or unsigned, it doesn't matter..
Signed: check if it's not below zero.
Unsigned check if it's not above 2^31-1
Both cases have advantages and disadvantaged.
Don't see this as a hate but in this case we are limited to the client which uses signed and because of that is there no real advantages of using unsigned over signed ints
Well I don't see this as hate as you might have a point maybe I just don't understand it well.
