10.1.2013 8:59, Ian Kelly kirjoitti:
On Wed, Jan 9, 2013 at 11:40 PM, Jani Tiainen wrote:
If we just force using force_unicode everything works except in older
versions of cx_Oracle (our server had 5.0.4 or something) connection strings
can't be unicode for some reason.
Sure, that's why the c
On Wed, Jan 9, 2013 at 11:40 PM, Jani Tiainen wrote:
> If we just force using force_unicode everything works except in older
> versions of cx_Oracle (our server had 5.0.4 or something) connection strings
> can't be unicode for some reason.
Sure, that's why the check exists in the first place. Pr
9.1.2013 19:21, Ian Kelly kirjoitti:
On Wed, Jan 9, 2013 at 3:55 AM, Jani Tiainen wrote:
Server is running Oracle Database 10g Release 10.2.0.5.0 - 64bit Production.
(EE edition)
and charset info:
NLS_CHARACTERSETWE8ISO8859P1
NLS_NCHAR_CHARACTERSET AL16UTF16
Sorry, I meant your web
On Wed, Jan 9, 2013 at 3:55 AM, Jani Tiainen wrote:
> Server is running Oracle Database 10g Release 10.2.0.5.0 - 64bit Production.
> (EE edition)
>
> and charset info:
> NLS_CHARACTERSETWE8ISO8859P1
> NLS_NCHAR_CHARACTERSET AL16UTF16
Sorry, I meant your web server setup.
--
You receive
9.1.2013 12:28, Ian kirjoitti:
On Wednesday, January 9, 2013 12:38:28 AM UTC-7, Jani Tiainen wrote:
Tested against latest master. Same behaviour.
In Oracle backend base.py is following piece of code:
# Check whether cx_Oracle was compiled with the WITH_UNICODE option.
This will
On Wednesday, January 9, 2013 12:38:28 AM UTC-7, Jani Tiainen wrote:
>
> Tested against latest master. Same behaviour.
>
> In Oracle backend base.py is following piece of code:
>
> # Check whether cx_Oracle was compiled with the WITH_UNICODE option.
> This will
> # also be True in Python 3.0.
Ok, found source of the problem - but I don't know the solution.
I'm using Oracle client 10.2.0.3.0. It seems that unicode doesn't work
there.
I compiled cx_Oracle against 11g instantclient 11.2 and it worked just fine.
So it must be something that Django assumes with Oracle and unicode
capa
Tested against latest master. Same behaviour.
In Oracle backend base.py is following piece of code:
# Check whether cx_Oracle was compiled with the WITH_UNICODE option.
This will
# also be True in Python 3.0.
if int(Database.version.split('.', 1)[0]) >= 5 and not hasattr(Database,
'UNICODE'):
8.1.2013 21:00, akaariai kirjoitti:
I created the following test case into django's test suite modeltests/
basic/tests.py:
def test_unicode(self):
# Note: from __future__ import unicode_literals is in
effect...
a = Article.objects.create(headline='0
\u0442\u0435\u0441\u0442
I created the following test case into django's test suite modeltests/
basic/tests.py:
def test_unicode(self):
# Note: from __future__ import unicode_literals is in
effect...
a = Article.objects.create(headline='0
\u0442\u0435\u0441\u0442 test', pub_date=datetime.n ow())
Hi,
I've been trying to save UTF-8 characters to oracle database without
success.
I've verified that database is indeed UTF-8 capable.
I can insert UTF-8 characters directly using cx_Oracle.
But when I use ORM it will trash characters.
Model I use:
class MyTest(models.Model):
txt = Cha
from django.conf.urls.defaults import patterns, include, url
from views import test
urlpatterns = patterns('',
url(ur'(?Pdom|działka|kamienica|biuro)/(?Pwynajem|
sprzedaż)/$', test, name='home'),
)
+
http://localhost.com:8000/dzia%25C5%2582ka/sprzeda%25C5%25BC/
I thought it would be more co
On Wednesday, April 13, 2011 9:31:27 PM UTC+1, Leszek Piątek wrote:
>
> Hi!
>
> I've recently came across problem in django. According to
> documentation I should be able to use unicode inside urlpatterns - but
> something is wrong I guess.
>
> When URL exists I got error displayed on dev serve
Hi!
I've recently came across problem in django. According to
documentation I should be able to use unicode inside urlpatterns - but
something is wrong I guess.
When URL exists I got error displayed on dev server console (no sigh
of problem), but IF URL DOESN'T exists error is printed out on webp
Karen, Thank you very much. Our collation is set to utf8_bin, which
was the source of the problem. Adam
On Aug 17, 9:01 pm, Karen Tracey wrote:
> 2010/8/17 adam
>
>
>
>
>
> > When I connect directly to mysql using the mysql client program, I see
> > that my table contains utf-8 data. Here are th
2010/8/17 adam
> When I connect directly to mysql using the mysql client program, I see
> that my table contains utf-8 data. Here are the environment settings:
>
> mysql> SHOW VARIABLES LIKE '%character%';
> [snip]
>
> However, when I access my model through the django shell, I have
> problems:
>
When I connect directly to mysql using the mysql client program, I see
that my table contains utf-8 data. Here are the environment settings:
mysql> SHOW VARIABLES LIKE '%character%';
+--
+-+
| Variable_name|
Value
gt;
> I am using MySQL. How to select UTF-8 encoding for the CharFields and
> TextFields in the models I create?
>
> Regards Ganesh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users&
Hi All,
I am using MySQL. How to select UTF-8 encoding for the CharFields and
TextFields in the models I create?
Regards Ganesh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
19 matches
Mail list logo
