C# & MySQL & SQL

This is so old that I forget what the issues were.

Tell you what, Severus. Try taking your own advice. Try providing some actual useful help. Can you do that?

What is the intended purpose of the field

As far as I am concerned, the problem is solved and it does not matter what the purpose is of the data.

If we are going to continue to discuss it, then can you please try doing what I requested?

I think the problem is the mysql.data.dll connect library file I downloaded from mysql. It has a bug. TinyInt(1) will treat as bool value. however if its TinyInt(2) or (3) then it is actual TinyInt

since its TinyInt(1), a bool value, so its either 0, False or 1~9, True

but if you add +0 it will convert to the int value 

David,  can you then tell me what it is for, this way we can then see what the problem really is.  How is 6 & 7 being put into the field!!

I didnt design the mysql db, so i didnt choose the datetype to store values beside 0,1

Vulpes, you are right that a TinyInt is a single byte integer and Bool, Boolean are synonyms for TinyInt(1) what I am failing to understand is why David is using a TinyInt for more than a bool value then going through the hassles of type conversion.  It is not as if there is a valid reason for using TinyInt for storing values other than 0, 1, a small int would do the job just the same as an int or even a single byte varchar(1) which is probably easier to convert to an int -- TryInt.Parse("7") than what he is now experiencing.

30 or 40 years ago memory and storage were at a premium so doing what David is doing would have been a valid reason but today memory and storage is not that much of a premium and you can easily afford to use a small int.

My question for David is what reason are you using TinyInt for other than true or false?  If you want to use a TinyInt for a 3 state check box then I can understand that but in this case you can have values 0, 1, 2, 2 being the third state why are you wanting to store 3,4,5,6,7,8, & 9!!

If I know that I will not be storing values > 9 I use an int or even a varchar in some cases but this depends on what I am doing with it.

Seems to me that by using TinyInt he is now working around a problem he would NOT have by using small int or int, my suggestion is convert the MySql field to an INT and be done with it..

Note that in this case, the body of the two threads are the same but the subjects are different and the forums are different. So the duplicates were intentional. When they are unintentional, the person doing the posting often closes one immediately, which can be done. David could have closed one of the threads but I assumed it was not worth the effort to ask for that.

David, I sure wish you had done what I suggested so we don't have to guess.

Vulpes, note that in the first reply I said that there is a duplicate. What more can we do? I usually add a link to the other thread but that is extra work. The problem is that theLizard did not see that reply either and replied to this thread. Could you other guys please explain to David that we don't appreciate people creating duplicate threads?

Problem Fixed This is How:

string sql = "SELECT (newNumber+0) AS abcd FROM tblSomeTable WHERE id = '29954' LIMIT 1";

int newNumber = Convert.ToInt32(reader["abcd"]);

Console.WriteLine(newNumber);

print out 6

problem has to do with the select statement by adding " (newNumber+0)" then everything is ok

Vulpes, note that the suggestion to cast to a Byte had already been suggested and the response was that it does not work.

I sure wish that David tried my last suggestion. Then he would know for sure what the C# data type is and then use that as the cast.

TinyInt is a bool 1 or 0, true or false