 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / DB Engine / SQL Server CE / September 2007Column Padding
Hello All, I just converted my 2.0 db to 3.0 and am running into problems where sqlce appears to be padding some of my columns which are varchars. For example my where clause "WHERE device_id = "1966" doesn't return anything while "WHERE device_id LIKE '%1966" and WHERE RTRIM(device_id) = "1966" does. I even checked the len by calling select LEN(device_id) and it did return 4. What am I doing wrong? Can anyone help? Mike, Is the double quote a typo? What do you get with WHERE device_id = '1966' ?  SignatureGinny Caughey Device Application Development MVP > Hello All, > [quoted text clipped - 5 lines] > > What am I doing wrong? Can anyone help? Yes it was a typo and I get nothing with Where device_id = '1966'. ALso, this appears to be isolated to sql server on the mobile. When ran on the mobile, I get nothing, then when I copy the sdf to my desk top and run it from sql management studio it runs fine? > Mike, > [quoted text clipped - 11 lines] >> >> What am I doing wrong? Can anyone help? Is this with SQLce 3.1? Thanks, SignatureGinny Caughey Device Application Development MVP > Yes it was a typo and I get nothing with Where device_id = '1966'. > [quoted text clipped - 17 lines] >>> >>> What am I doing wrong? Can anyone help? One other question, is the data type varchar or nvarchar? Do you have a small sample that reproduces it including the part that creates the sdf file? SignatureGinny Caughey Device Application Development MVP > Is this with SQLce 3.1? > [quoted text clipped - 21 lines] >>>> >>>> What am I doing wrong? Can anyone help? I am using SQLCE 3.0 The data type is a nvarchar(10). I am not 100% sure what you mean, basically to repoduce it, all I have to do is a select * from table where device_id = '1966' using the Query Analyzer 3.0 on the handheld or even when it is called from code on the handheld. Then if I copy the sdf to my desktop and then run the exact same query using management studio, it works fine. As for creating the DB, I used the upgrade utility to convert it from 2 to 3. > One other question, is the data type varchar or nvarchar? Do you have a > small sample that reproduces it including the part that creates the sdf [quoted text clipped - 25 lines] >>>>> >>>>> What am I doing wrong? Can anyone help? Ok thanks. SignatureGinny Caughey Device Application Development MVP >I am using SQLCE 3.0 > [quoted text clipped - 38 lines] >>>>>> >>>>>> What am I doing wrong? Can anyone help? I think I am getting closer to the cause of it. I upgraded the DB and then ran the sql (select * from table where device_id = '1966' ). I then modified the table using management studio (I added a column ID as a primary key with identity set to true and I begin having this problem. > Ok thanks. > [quoted text clipped - 40 lines] >>>>>>> >>>>>>> What am I doing wrong? Can anyone help? Do you still have the problem if you do a Repair/Compact on the database? I don't know why adding a column should cause your select statement to begin failing unless the database has become corrupted. Do you get any error message, or does it just not return any rows? SignatureGinny Caughey Device Application Development MVP >I think I am getting closer to the cause of it. I upgraded the DB and then >ran the sql (select * from table where device_id = '1966' ). I then [quoted text clipped - 45 lines] >>>>>>>> >>>>>>>> What am I doing wrong? Can anyone help? I will have to compacting / repairing it to see if that helps. Also, no, I do not get any errors, it just returns nothing. > Do you still have the problem if you do a Repair/Compact on the database? > I don't know why adding a column should cause your select statement to [quoted text clipped - 50 lines] >>>>>>>>> >>>>>>>>> What am I doing wrong? Can anyone help? Okay, I just compacted / repaired the DB and that did not help. > Do you still have the problem if you do a Repair/Compact on the database? > I don't know why adding a column should cause your select statement to [quoted text clipped - 50 lines] >>>>>>>>> >>>>>>>>> What am I doing wrong? Can anyone help? Ok, here's another question: can you reproduce the same behavior in a new database? SignatureGinny Caughey Device Application Development MVP > Okay, I just compacted / repaired the DB and that did not help. > [quoted text clipped - 52 lines] >>>>>>>>>> >>>>>>>>>> What am I doing wrong? Can anyone help? No, it only appears to start happening after I modify it with the management studio. > Ok, here's another question: can you reproduce the same behavior in a new > database? [quoted text clipped - 55 lines] >>>>>>>>>>> >>>>>>>>>>> What am I doing wrong? Can anyone help? Ok, thanks, Mike. SignatureGinny Caughey Device Application Development MVP > No, it only appears to start happening after I modify it with the > management studio. [quoted text clipped - 62 lines] >>>>>>>>>>>> >>>>>>>>>>>> What am I doing wrong? Can anyone help? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.