lat=True)
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On
Behalf Of Jakob Karstens
Sent: Tuesday, October 9, 2018 11:58 AM
To: Django users
Subject: Re: psycopg2 Substr SQL generator bug?
Unfortunately, using the `output_field` keyword argument leads to the same
error:
&
he output_field argument .
>
> Conference.objects.annotate(year=ExtractYear('start_date',
> output_field=CharField())).filter(website__contains=F('year'))
>
>
>
> *From:* django...@googlegroups.com [mailto:
> django...@googlegroups.com ] *On Behalf Of *J
Jakob Karstens
Sent: Tuesday, October 9, 2018 11:43 AM
To: Django users
Subject: Re: psycopg2 Substr SQL generator bug?
Thanks Matthew, I'll submit a ticket.
Unfortunately, ExtractYear does not return a string, so it seems like I would
still need to explicitly cast the ye
Thanks Matthew, I'll submit a ticket.
Unfortunately, ExtractYear does not return a string, so it seems like I
would still need to explicitly cast the year annotation to a string:
>>> Conference.objects.annotate(year=ExtractYear('start_date')).filter(
website__contains=F('year'))
Traceback (most
I would submit a ticket for that issue.
Also, instead of using string functions to solve your problem, I would use the
ExtractYear function.
Conference.objects.annotate(year=ExtractYear('start_date')).filter(website__contains=F('year'))
From: django-users@googlegroups.com [mailto:django-users@
Thanks Mario, it worked
2014-07-24 21:56 GMT-03:00 Mario Gudelj :
> In
> http://stackoverflow.com/questions/20789063/get-fatal-error-when-install-psycopg2
> OP mentions that "Just installed python 3.4 and assumed python3-dev would
> suffice. Nope. Had to do python3.4-dev. "
>
> Perhaps you need
In
http://stackoverflow.com/questions/20789063/get-fatal-error-when-install-psycopg2
OP mentions that "Just installed python 3.4 and assumed python3-dev would
suffice. Nope. Had to do python3.4-dev. "
Perhaps you need to do the same thing...
On 25 July 2014 10:29, Henrique Oliveira
wrote:
> H
Hi Mario,
I already installed python-dev
On Jul 24, 2014 9:11 PM, "Mario Gudelj" wrote:
> Install this first:
>
> sudo apt-get install python-dev
>
> Then try installing that package again.
>
>
> On 25 July 2014 09:55, Henrique Oliveira
> wrote:
>
>>
>>
>>
>>
>>
>> *Hi All,I am trying to instal
Install this first:
sudo apt-get install python-dev
Then try installing that package again.
On 25 July 2014 09:55, Henrique Oliveira
wrote:
>
>
>
>
>
> *Hi All,I am trying to install psycopg2 but I am getting this error:*I
> already installed python3-dev and libpq-devAny idea?*
>
> Downloadin
On 2013-11-10, at 1:16 AM, Matthias Fripp wrote:
> I had the same problem. I am trying to make this work on a multi-user
> machine. My two options seem to be
Neither seem good. I install most required packages which are not handled by
pip using MacPorts (Homebrew works fine too afaik).
This
I had the same problem. I am trying to make this work on a multi-user
machine. My two options seem to be
(1) Add this line to /etc/profile:
export DYLD_LIBRARY_PATH=/Library/PostgreSQL/9.3/lib
The disadvantage of this is that changing DYLD_LIBRARY_PATH doesn't seem to
be a common technique on
One problem you are having is a typographical error: The cursor method is
"Fetch One" not "Fetch None".
On Friday, November 1, 2013 8:46:17 AM UTC+1, hjr1 wrote:
>
> Hi all.
>
> I am trying to use django.db.connection with psycog2 (postgres). I can run
> something like cursor=connection.curs
> I just had this exact same problem and it took me a while to find the
> solution.
>
> On OSx there is a separate library path variable for .dylib library files. I
> added the following to my .bashrc (or.bash_env or however you set up your
> shell environment).
>
> export
> DYLD_LIBRARY_PATH="/usr
Good afternoon,
I just had this exact same problem and it took me a while to find the
solution.
On OSx there is a separate library path variable for .dylib library files.
I added the following to my .bashrc (or.bash_env or however you set up your
shell environment).
export
DYLD_LIBRARY_PATH=
On 2013-10-27, at 7:46 AM, Doug Snyder wrote:
> I don't have a very specific answer for your question. I just started doing
> my django dev on OSX coming from Ubuntu
> My understanding is that Home Brew is a better solution than Mac Ports, I
> have heard some people being very critical of Mac
Thanks for the response. I only mentioned MacPorts to demonstrate that when
psycopg2 was built, pip couldn't have found libssl 1.x there. I routinely build
my own Python instances. The venv version of Python is a 2.7.5+ version built
from hg.
Skip
--
You received this message because you are
I don't have a very specific answer for your question. I just started doing
my django dev on OSX coming from Ubuntu
My understanding is that Home Brew is a better solution than Mac Ports, I
have heard some people being very critical of Mac Ports which I think was
once the best solution for python e
On Tue, Jan 1, 2013 at 12:30 PM, hu mingchun wrote:
> add localhost to host field in settings.py
>
> 在 2009年6月24日星期三UTC+8上午10时09分25秒，Chris Haynes写道：
>>
>> I've just installed postgresql and psycopg2. I supplied a password in
>> the postgres install, but don't know how to supply it to psycopg2:
>>
add localhost to host field in settings.py
在 2009年6月24日星期三UTC+8上午10时09分25秒，Chris Haynes写道：
>
> I've just installed postgresql and psycopg2. I supplied a password in
> the postgres install, but don't know how to supply it to psycopg2:
>
> ~/s/sd$ manage.py syncdb
> Traceback (most recent call l
A very useful resource for Windows users is
http://www.lfd.uci.edu/~gohlke/pythonlibs/
... where you can download the compiled psycpg2 package you need.
Also, I prefer pip rather than easy-install
Good luck.
Mike
On 18/11/2012 6:36pm, Jun Tanaka wrote:
Thank you for your advise. I used t
Thank you for your advise. I used the trace back and it says
'exceptions.ImportError'. On Windows, cay you not easy_install psycopg2?
When I did, it seems that it was done correctly.
Please help!!!
2012年11月18日日曜日 2時11分23秒 UTC+9 ovnicraft:
>
>
>
>
> On Sat, Nov 17, 2012 at 11:07 AM, Jun Ta
On Sat, Nov 17, 2012 at 11:07 AM, Jun Tanaka wrote:
> I run a django program with psycopg2 on Mac and then it works fine. Now, I
> am trying to run the same program on Windows. Then "ImportError: No module
> named psycopg2.extensions" shows up. I installed the same version of
> django, postgres,
On Tue, Oct 30, 2012 at 6:06 AM, jondbaker wrote:
> When I run 'python manage.py validate' the following error is returned:
>
> psycopg2.DataError: invalid value for parameter "TimeZone": "UTC"
>
> settings.py
> TIME_ZONE = 'America/Denver'
> USE_TZ = True
>
> I'm using Django 1.4.2 with Postgres
And to whomever wrote and applied those very patches, _thank you_. I discovered
them after shifting to 1.4a and suddenly lots of things just work.
-WBTD.
On 23 Feb 2012, at 01:26, Jeff Heard wrote:
> Just as a followup to this, there are a few problems that have been patched
> on Django with r
Just as a followup to this, there are a few problems that have been patched
on Django with regards to Postgres 9.1. They're not in the stable release,
but if you're using custom binary fields, such as PostGIS geometry, you
will need to search for the patch and apply it. You may see '\x00' is not
You can either add the proper path of pg_config to your PATH, or just
extract the psycopg2 and add the full path to pg_config into the config
file it contains then run 'python setup.py install' on the setup.py in
the package.
--
You received this message because you are subscribed to the Googl
Thanks for providing this feedback, Tom. I read your original question but I
wasn't sure of the answer, so it's good to know how you worked it out!
Best regards,
AT
On Wed, Sep 28, 2011 at 4:51 AM, tom wrote:
> Hello,
>
> I have solved the problem with the support from newrelic, the issue was
>
Hello,
I have solved the problem with the support from newrelic, the issue was
related to the configuration of wsgi. I have 3 VHosts for the application. I
switched from wsgi embedded mode to daemon mode. Additionally I have added
these two lines for each VHost:
WSGIDaemonProcess www.agileamp.
So, it works if I patch
django.contrib.gis.db.backends.postgis.adapter. But that's obviously
*not* the way to go...
class PostGISAdapter(object):
...
def getquoted(self):
"Returns a properly quoted string for use in PostgreSQL/
PostGIS."
# Want to use WKB, so wrap with psy
Wiadomość napisana w dniu 2009-12-10, o godz. 13:41, przez Alexander
Dutton:
> As of last Thursday we've been seeing ~100% CPU usage from Apache,
> which
> we believe was caused by Debian Bug #528529[0], whereby psycopg2 was
> attempting to double free pointers, resulting in segfaults. This wa
Hi Alexander,
I wanna to ask you how do you configure django debian postgres apache and
psycopg2
i try it but i could not have i wanan to run it on apache with svn .
Thanks
- Mail Original -
De: "Alexander Dutton"
À: django-users@googlegroups.com
Envoyé: Jeudi 10 Décembre 2009 12h41:41
That is another forum and postgresql question, and they provide fantastic
documentation:
http://www.postgresql.org/docs/8.1/static/sql-createrole.html
I use pd-Admin tool myself to totally control the database.
I would suggest think you make sure you are able to play around with the
database first
How exactly did you put your database user? What is content of your
pg_hba.conf?
Maybe some parts of this could be helpful:
http://sharpe-s-postgres.blogspot.com/2009/09/how-to-install-and-configure-postgresql.html/
On Sep 7, 11:15 pm, Zico wrote:
> On Tue, Sep 8, 2009 at 3:06 AM, Angel Cruz wr
-users@googlegroups.com
Cc: mrangelc...@gmail.com
Subject: Re: psycopg2.OperationalError: FATAL: role "root" does not exist
On Tue, Sep 8, 2009 at 3:06 AM, Angel Cruz wrote:
You don't have a user account named 'root' in your database. You should
probably use
On Tue, Sep 8, 2009 at 3:06 AM, Angel Cruz wrote:
>
> You don't have a user account named 'root' in your database. You should
> probably use another user besides root. Change your settings.py file to
> the
> correct database user?
>
Ok, if i put my database user "fixmystreet" .. which is the e
You don't have a user account named 'root' in your database. You should
probably use another user besides root. Change your settings.py file to the
correct database user?
-Original Message-
From: django-users@googlegroups.com [mailto:django-us...@googlegroups.com]
On Behalf Of Zico
Sent
I think combo of these links should help you,
http://hocuspokus.net/2008/05/install-postgresql-on-ubuntu-804
find out where pg_hba.conf
should be under your 8.3/main/ , I am not sure just find it out. This file
has all the permission stuff.
Also otherwise look at docs
http://www.postgresql.org/d
There are some solutions posted here, maybe it would help you.
http://lethain.com/entry/2009/feb/13/when-psycopg2-can-t-import-tz/
--
With kind regards,
Petar Radosevic
W: wunki.org
PGP Fingerprint: CCDD 7545 4907 D40D C0AC 3AC2 FDDC 2E15 AC44 2A15
PGP Publickey : http://wunki.org/pgp/
pgp
Yes they were able to help me fix the problem.
Thank you Peter.
On Nov 17, 1:00 pm, "Peter Herndon" <[EMAIL PROTECTED]> wrote:
> Hi DJ,
>
> Psycopg2 has a C extension wrapped by Python. That C extension must
> be compiled with the same compiler used to compile the Python compiler
> itself.
>
> T
Hi DJ,
Psycopg2 has a C extension wrapped by Python. That C extension must
be compiled with the same compiler used to compile the Python compiler
itself.
This is not a Django issue, this is a psycopg issue. You should ask
for assistance on the psycopg mailing list, they'll be better able to
he
>
>
> I'm afraid I don't have any magic solutions. The best approach I can
> suggest is to log the SQL that is being executed (either in the
> Postgres query log or by putting in some debug statements into Django
> to output connection.queries). Then narrow down the statement that is
> causing prob
On Wed, Aug 20, 2008 at 11:26 AM, Chris Moffitt <[EMAIL PROTECTED]> wrote:
> I am seeing this error - http://dpaste.com/72596/ with django trunk (rev
> 8445) when I try to run syncdb using psycopg2 but it works just fine if I
> use sqlite.
>
> Basically I'm getting an error when doing the table in
On Jun 25, 4:00 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Why not put it up on Google Code? It's SVN so importing should be a
> breeze (if not, I'm sure the Google guys would be glad to lend a
> hand), you have a Wiki and a Bug tracker also.
I will never, *ever*, put my code in a syste
On Fri, Jun 27, 2008 at 6:19 AM, Will <[EMAIL PROTECTED]> wrote:
> Ah, sorry. Reading the Django book had led me to believe I was stuck
> with psycopg:
The change which allows user-defined backends to be plugged in
happened after the 0.96 release, so the book is accurate for 0.96.
--
"Bureaucr
> Erm... the database backends _are_ pluggable. Hence, the
> DATABASE_ENGINE setting.
>
Ah, sorry. Reading the Django book had led me to believe I was stuck
with psycopg:
http://www.djangobook.com/en/beta/chapter05/
>DATABASE_ENGINE tells Django which database engine to use. If you’re using a
On Fri, Jun 27, 2008 at 3:06 AM, Will <[EMAIL PROTECTED]> wrote:
> Would I have to write an entire new backend for postgres, just to use
> a different driver?
You'd need a module that implements the interface of a Django database
adapter while using another driver. A few months ago I saw an artic
On Jun 26, 11:38 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> Erm... the database backends _are_ pluggable. Hence, the
> DATABASE_ENGINE setting.
>
I undersand that, but I'm stuck with psycopg or psycopg2 if I'm to use
postgres, aren't I?
Would I have to write an entire new backend f
On Thu, Jun 26, 2008 at 10:05 PM, Will <[EMAIL PROTECTED]> wrote:
>
> Couldn't Django be pluggable with respect to the Database drivers?
> There's a DBAPI2 interface spec, therefore it should be possible.
Erm... the database backends _are_ pluggable. Hence, the
DATABASE_ENGINE setting.
If you wa
Perhaps there's another problem here.
As far as I know, Django doesn't support the pygresql or pg/python
drivers.
http://python.projects.postgresql.org/ A very trustworthy looking
website :)
http://www.djangoproject.com/documentation/design_philosophies/
>Loose coupling
>A fundamental goal of D
A suggestion for those of you who like psycopg2 and want a fancier
site to show yr pointy-haired boss:
make one. Either on your own, linked to the project site, or
contribute to the project site (with the permission of the
developer(s)).
--~--~-~--~~~---~--~~
You r
Hi,
Everything is about buying and selling something. If I work in software
development company, use python, postgresql and want to use psycopg2 - nice
web page helps in "selling" the idea of using psycpg2 to my boss. Of course,
nice website is not the only important thing but it helps a lot.
Peop
Well, I disagree.
Not with the idea that a decent support site is good for software,
but that you, or anyone, has any right whatsoever to expect anything at
all from people who are taking their own time out of their lives to
build & support pieces of software that they then give away.
You make a
Even if it had the most beautiful site in the world, and that was enough to
get permission to use it, a responsible developer would write some unit
tests and check the items that he asked in his original question.
His highly-qualified scientists probably won't have any idea that a database
driver
I agree with Will on this one. While it's not the site that makes the
software, it sure as heck determines how many people (and companies)
will take that first chance and use it.
psycopg2 might be the best thing since sliced bread. I've always used
MS SQL and MySQL. Recently, I've started lear
Hi,
To be honest, I would rather the developers concentrate on the code than
on the website. I'm already very thankful that they're doing such
fantastic work.
I'm all for a simple solution like Google Code that takes care of
everything.
If it's at all possible, it would be nice if someone fr
Why not put it up on Google Code? It's SVN so importing should be a
breeze (if not, I'm sure the Google guys would be glad to lend a
hand), you have a Wiki and a Bug tracker also.
Just my 2c
On Jun 24, 7:09 pm, Federico Di Gregorio
<[EMAIL PROTECTED]> wrote:
> Just to shed a bit of light:
>
> On
On Jun 24, 4:56 pm, Christian Joergensen <[EMAIL PROTECTED]> wrote:
> The problem with SQL injections shouldn't IMHO be solved at driver
> level, but is an application level problem.
This is plain wrong, especially if you want to support more than a
single backend in your application. The driver
> The problem with SQL injections shouldn't IMHO be solved at
> driver level, but is an application level problem.
The SQL driver is responsible for accuracy in the implementation
of safe methods for escaping and/or parameter substitution, and
the application is responsible for making proper us
Thanks for taking the time to write that, Federico.
My worries stemmed from my not being able to find any clear
information on psycopg, but I feel a lot happier now.
Cheers
Will
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
Just to shed a bit of light:
On Jun 24, 4:28 pm, Will <[EMAIL PROTECTED]> wrote:
> Is that substitute for a full suite of regression tests? What about
> buffer overflow attacks? There's probably loads of other attacks I
> don't even know about.
> It doesn't even sound as if psycopg gets tested b
On Jun 24, 7:06 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 24, 2008 at 12:20 PM, Will <[EMAIL PROTECTED]> wrote:
> > I really didn't want to turn this into a fight, and I apologise if my
> > posts have seemed inflammatory. I'd just like to be able to trust all
> > my stack.
>
On Tue, Jun 24, 2008 at 12:20 PM, Will <[EMAIL PROTECTED]> wrote:
> I really didn't want to turn this into a fight, and I apologise if my
> posts have seemed inflammatory. I'd just like to be able to trust all
> my stack.
Well, this is the thing: are you going to this level of detail on
*every*
I really didn't want to turn this into a fight, and I apologise if my
posts have seemed inflammatory. I'd just like to be able to trust all
my stack.
Will
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django u
Will wrote:
>> You're not asking it to do a whole hell of a lot.
>
> In terms of security, perhaps this is the most critical part of the
> stack? SQL injection is one of the nastiest security vulnerabilities
> IMHO.
The problem with SQL injections shouldn't IMHO be solved at driver
level, but i
On Tue, Jun 24, 2008 at 11:28 AM, Will <[EMAIL PROTECTED]> wrote:
> All I'm asking for is some reason to trust the integrity of psycopg,
> and all I'm getting from you is sarcasm. Perhaps you could provide me
> with some links?
psycopg is used, happily, by everyone from hobbyists to Fortune 500
c
Django is known for and designed to be *flexible.* If you don't like
how a certain stack is made, make it better.
It's one of Django's core philosophies.
Sent from my iPhone
On Jun 24, 2008, at 9:28, Will <[EMAIL PROTECTED]> wrote:
>
> Michael,
>
>>> In terms of security, perhaps this is the
>> You don't have time to write 2-3 bad SQL queries and attempt
>> injection? We're talking 5 lines of python, and that includes import
>> statements.
> It doesn't even sound as if psycopg gets tested before release.
> All I'm asking for is some reason to trust the integrity of psycopg,
> and a
Michael,
> > In terms of security, perhaps this is the most critical part of the
> > stack? SQL injection is one of the nastiest security vulnerabilities
> > IMHO.
>
> You don't have time to write 2-3 bad SQL queries and attempt
> injection? We're talking 5 lines of python, and that includes imp
> In terms of security, perhaps this is the most critical part of the
> stack? SQL injection is one of the nastiest security vulnerabilities
> IMHO.
You don't have time to write 2-3 bad SQL queries and attempt
injection? We're talking 5 lines of python, and that includes import
statements.
I can
>You're not asking it to do a whole hell of a lot.
In terms of security, perhaps this is the most critical part of the
stack? SQL injection is one of the nastiest security vulnerabilities
IMHO.
>Seriously, though, psycopg2 is an open source library with a history of
>working pretty well for what
> Why should we trust psycopg2 to be a high quality piece of software?
>
You're not asking it to do a whole hell of a lot. No computation.
Simply "take A and put it in B" or "get B from A." I don't know why
you'd expect this little connection piece to have a large team of
support behind it.
Th
Well, in keeping with the spirit of the link referenced, at least its not
trac!
Seriously, though, psycopg2 is an open source library with a history of
working pretty well for what it does. AFAIK there is not a great deal of
money behind it, and so they may not have the prettiest or most useful,
On Jan 2, 2008 12:07 AM, LRP <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm trying to install django following directions in The Django Book.
> I would like to run with Postgres on my Debian etch system.
>
> When I try to build psycopg2.0.6 I get the error messages shown below.
> Would much appreci
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malcom,
The steps to repeat this problem is simply to invoke 'syncdb'
using either django-admin.py and/or manage.py, on a fresh database:
1. export PYTHONPATH=`pwd`:/path/to/django (optional)
2. sudo dropdb -U db_user db_name
3. sudo createdb -U
On Tue, 2007-07-10 at 10:51 -0400, Etienne Robillard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Hi all,
>
> I'm running into an issue using the latest psycopg2 module from svn.
> Is there a way to have this module working with the latest django-trunk
> and postgresql-8.1.9
I can confirm that this bug is still happening in both django-trunk
and 5528:
Here's the traceback message when using django 5528:
[36450] conn_notice_callback: NOTICE: CREATE TABLE / PRIMARY KEY will
create im plicit index "auth_group_permissions_pkey" for table
"auth_group_permissions"
On Mon, 2007-06-25 at 13:09 +1000, Malcolm Tredinnick wrote:
> On Sun, 2007-06-24 at 20:07 +, yuccaplant wrote:
> > I'm new to Django and I suspect I did something wrong. Whenever I do
> >
> > python manage.py syncdb
> >
> > I get these kind of errors:
> >
> > psycopg2.ProgrammingError: rel
On Sun, 2007-06-24 at 20:07 +, yuccaplant wrote:
> I'm new to Django and I suspect I did something wrong. Whenever I do
>
> python manage.py syncdb
>
> I get these kind of errors:
>
> psycopg2.ProgrammingError: relation "auth_message" already exists
>
> which is of course true, because I
Hm.. I suppose that if you change the name of model it'll be okay.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscr
postgresql-8.2.3 and psycopg2-2.0.5.1.win32-py2.5-pg8.2.0
2007/4/28, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
>
> On Sat, 2007-04-28 at 20:39 +0800, li liren wrote:
> > In django I use psycopg2 to connect to postgresql
> > I test the DB setting in setting.py：
> > >>> from django.db import connne
On Sat, 2007-04-28 at 20:39 +0800, li liren wrote:
> In django I use psycopg2 to connect to postgresql
> I test the DB setting in setting.py：
> >>> from django.db import connnection
> >>> cursor = connection.cursor()
>
> psyco_connect: dsn = 'user= dbname=test password='''
> connec
On 04-Mar-07, at 12:33 PM, Malcolm Tredinnick wrote:
>>
>> Are there any advantages to using psycopg2 in a Django project?
>
> One reasonable argument is that it is the maintained version of the
> PostgreSQL-python bindings, whereas psycopg (version 1.x) is no longer
> maintained. If you need to
On Sat, 2007-03-03 at 08:47 -0500, Ross M Karchner wrote:
> On 2/28/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >
> > On 2/28/07, Robert <[EMAIL PROTECTED]> wrote:
> > > On 28 Lut, 16:18, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> > >
> > > >
> > > > Change your DATABASE_ENGINE to "postgresql_p
On 2/28/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On 2/28/07, Robert <[EMAIL PROTECTED]> wrote:
> > On 28 Lut, 16:18, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > Change your DATABASE_ENGINE to "postgresql_psycopg2".
Are there any advantages to using psycopg2 in a Django projec
On 2/28/07, akonsu <[EMAIL PROTECTED]> wrote:
>
> hello,
>
> my host has psycopg2 and does not have psycopg. is there a way to use
> that? i have django installed as local module in my user directory so
> i can tweak it if needed.
Change your DATABASE_ENGINE to "postgresql_psycopg2".
(Perhaps th
On 2/28/07, Robert <[EMAIL PROTECTED]> wrote:
> On 28 Lut, 16:18, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
> >
> > Change your DATABASE_ENGINE to "postgresql_psycopg2".
> >
> > (Perhaps the docs and default settings file should be updated to reflect
> > this.)
>
> It is :-)
>
> http://www.djan
On 28 Lut, 16:18, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
> Change your DATABASE_ENGINE to "postgresql_psycopg2".
>
> (Perhaps the docs and default settings file should be updated to reflect
> this.)
It is :-)
http://www.djangoproject.com/documentation/install/
--
Robert
--~--~---
( still in beta yada yada yada ) <- that'd be the diatribe on the django site. so even though psycopg is stable it still officially isn't supported by the django developers. so anybody using it still has to eat their own pie.. h pie, I like pie.
VanceOn 8/11/06, Laurent Rahuel <[EMAIL PR
Le mercredi 9 août 2006 19:42, Vance Dubberly a écrit :
>
> Warning psycopg2 is not supported by django. ( still in beta yada
> yada yada ). Unless you're willing to eat your own pie when things go
> awry, don't use it.
>
Snip,
Fromhttp://initd.org/projects/psycopg2, you can read :
"""
psycop
Not much difference between it and any other database due to django's
ORDBM. The only difference during set up is that instead of setting
the db to postgres you set it as such
DATABASE_ENGINE = 'postgresql_psycopg2'
If you didn't do it already you might want to follow the the last Q on
this FAQ h
yes you can, in your settings file:
DATABASE_ENGINE = 'postgresql_psycopg2'
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
T
Thank you much! VanceOn 7/30/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
On 7/30/06, Vance Dubberly <[EMAIL PROTECTED]> wrote:> postgresql_psycopg2>> Yes I found it. Yes I know it's not supported . But could somebody tell me
> how to tell it to shut up? My eyes are bleeding! :) The debug output is> j
On 7/30/06, Vance Dubberly <[EMAIL PROTECTED]> wrote:
> postgresql_psycopg2
>
> Yes I found it. Yes I know it's not supported . But could somebody tell me
> how to tell it to shut up? My eyes are bleeding! :) The debug output is
> just a little overwhelming and quite useless unless you are the mo
Adrian Holovaty wrote:
> From the looks of that traceback, you're using the "postgresql"
> backend rather than the "postgresql_psycopg2" backend. To use Django
> with psycopg2, make sure your DATABASE_ENGINE setting is set to
> 'postgresql_psycopg2'.
True, problem fixed.
Thanks Adrian,
Lorenzo
On 7/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'm receiving the following error:
>
> C:\www\myproject>python manage.py sql user
> Traceback (most recent call last):
> File "manage.py", line 11, in ?
> execute_manager(settings)
> File
> "c:\python24\lib\site-packages\django-0.9
95 matches
Mail list logo
