[ Prokleta_Nedelja @ 18.03.2008. 10:32 ] @
Kupio sam hosting kod www.datapacket.net i sto se tice resursa, zadovoljan sam. Problem mi se javlja kada iz baze (koja cuva podatke u utf8 formatu) ucitam nesto preko ODBC-a tada dobijam ovo http://www.svsavars.org
Ukoliko te podatke ucitam preko MySQL.NET konektora onda je sve ok sto mozete vidjeti na ovoj strani: http://www.svsavars.org/detaljno.aspx?id=9
connection string za odbc koji sam koristio je: Driver={MySQL ODBC 3.51 Driver};server=localhost;database=moja_baza;uid=moje_ime;pwd=moja_sifra;option=3;stmt=SET NAMES 'cp1250'

pokusavao sam da cp1250 zamjenim sa utf8 ali ne ide...

stavio sam u web.config
<globalization uiCulture="sr-Latn-CS" culture ="sr-Latn-CS" requestEncoding ="utf-8" responseEncoding ="utf-8"/>
ali i dalje ne ide...

valjda imate neko rjesenje...

[ mmix @ 19.03.2008. 21:56 ] @
OK, izvini na bukvalnom odgovoru, ali sto ne koristis MySQL.NET za sve kad vec radi?

Ako ne, ovo sam nasao na mysql supportu:

MyODBC 3.51 was never meant to be unicode aware so it maps unicode (W) functions into non-unicode counterpart thus resulting in "wrong" characters returned.

connector/ODBC 5 is to have full unicode support but it's still in beta. So I don't really see that "nothing is done". We have made entirely new connector that should solve this problem once it's out of testing stage.


Mozda da isntaliras novi ODBC konektor?
[ Prokleta_Nedelja @ 19.03.2008. 22:39 ] @
Citat:
ali sto ne koristis MySQL.NET za sve kad vec radi?

jer moram onda da rucno radim Paging sa gridview i datalist kontrolama i moram da ispravim mnogo stranica, uh mnogo posla koji mi se cini bespotreban.
[ Burgos @ 19.03.2008. 23:26 ] @
Džaba ti to... MyODBC (ako želiš da se preko njega vežeš na bazu, a tako sam razumeo) ne radi sa UTF-8 stringovima (kao ni mysql++, nažalost :(, ali to nije sad tema)...
[ Prokleta_Nedelja @ 20.03.2008. 05:57 ] @
Kako ne radi? Evo ovdje http://www.adresar.ba/ imam bazu koja je utf8 a sve sam lijepo ucitao sa odbc-om
[ Burgos @ 20.03.2008. 13:59 ] @
MyODBC?
[ Prokleta_Nedelja @ 20.03.2008. 20:39 ] @
Naravno, pomenuli smo da je MyODBC
[ Burgos @ 21.03.2008. 00:02 ] @
Sad sam stvarno zbunjen :-|.. A evo i zvanicnog stava develop tima:

Citat:


This is a bug that we can't fix in 3.51.x - it is not written to handle multiple character
sets, or to handle many of the features of MySQL 4.1.

A new version, 3.53 (3.52 will not be released), will be available as an alpha release
soon, and it will eventually be fully compliant with the MyODBC spec, and will support all
MySQL features.

Our priority now is 3.53 development (while solving critical bugs in 3.51.x which deal
with existing functionality).
[ Prokleta_Nedelja @ 28.03.2008. 09:36 ] @
Skontah sta treba da bi ODBC 3.51 pravilno ucitao UTF8 treba na serveru podesiti regionalne postavke, sto niko iz www.datapacket.net nece ni u ludilu uraditi. Ostaje mi ili prepravka na MySQL.NET konektor ili prelazak na MSSQL