Wow, I think I just figured out what this is about. He's asking if
Django creates queries like
1) "SELECT id, song FROM songs WHERE id = 1"
or
2) "SELECT id, song FROM songs WHERE id = ?", and the passing in the 1
as a parameter.
He says that he saw a query like the first case, and is wondering
Carl Karsten wrote:
> The reason it sounds strange is because that isn't what I was asking :)
>
> It is pretty much this simple:
>
> import settings
> import MySQLdb
>
> con = MySQLdb.connect(user=settings.DATABASE_USER,
> passwd=settings.DATABASE_PASSWORD,
> db=settings.DATABASE_NAME )
On 7/12/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>
> Jacob Kaplan-Moss wrote:
> > OK, we're 8 messages deep into this thread, and I've got no idea what
> > the point is.
> >
> > Carl -- what is it you want to know? Is something not working
> > correctly for you, or is this just an academic
On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>
> Jacob Kaplan-Moss wrote:
> > OK, we're 8 messages deep into this thread, and I've got no idea what
> > the point is.
> >
> > Carl -- what is it you want to know? Is something not working
> > correctly for you, or is this just an academic
Jacob Kaplan-Moss wrote:
> OK, we're 8 messages deep into this thread, and I've got no idea what
> the point is.
>
> Carl -- what is it you want to know? Is something not working
> correctly for you, or is this just an academic question?
>
When I see SQL parameters being put into the SQL
On 7/12/07, leif strickland <[EMAIL PROTECTED]> wrote:
>
> Anyone? I've seen at least two threads related to this subject; I know
> I'm not the only one wondering.
Apologies for not getting back to you on this - I've been meaning to
take a look at the problem you are reporting, but I keep
On 7/11/07, mario__ <[EMAIL PROTECTED]> wrote:
>
> On 11 jul, 00:09, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
> >
> > Can you help out a little bit here by providing a test case (not
> > necessarily a unit test - just a clear set of instructions for how to
> > generate they type of
On Thu, Jul 12, 2007 at 08:45:33AM +0700, Yuri Baburov wrote:
> Can't do experiments now, but my admin interface (django trunk) began
> to work right after this middleware addition, that meant reverse url
> were resolved somehow.
> Snippet exactly change req.uri to req.script_name+req.uri, that
Hi Doug, Forest,
Can't do experiments now, but my admin interface (django trunk) began
to work right after this middleware addition, that meant reverse url
were resolved somehow.
Snippet exactly change req.uri to req.script_name+req.uri, that gives
req.path. Am I right? If I'm not, you can
Yes, word for word damnit!
Wish I'd seen that before I started messing... Still it taught me a bit more
about postgres I guess so it's all good! :-)
Cheers,
Ben
On 12/07/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
>
> Ben Ford wrote:
> > Peter,
> > I ran into this problem when I was bringing the
Ben Ford wrote:
> Peter,
> I ran into this problem when I was bringing the multi-db branch up to date
> and was so busy I forgot to tell anyone! (My bad) I fixed it, but it was on
> another machine. It's a pretty simple change, but the exact diff escapes me
> at the moment! Is there a ticket on
OK, we're 8 messages deep into this thread, and I've got no idea what
the point is.
Carl -- what is it you want to know? Is something not working
correctly for you, or is this just an academic question?
Jacob
--~--~-~--~~~---~--~~
You received this message
On 7/11/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/4615 has been waiting for checkin
> for a while. Could a committer please review it?
Done; thanks for the heads-up.
Jacob
--~--~-~--~~~---~--~~
You received this message
On Wed, Jul 11, 2007 at 09:27:43PM -, [EMAIL PROTECTED] wrote:
>
> This snippit replaces the request.path. My question is, how does this
> work with sitemap, absolute rul's and reverse url lookups? doesn't it
> break all of those, or am I missing something?
More importantly (for me), this
Is there any reason why its storing the keys in QueryDict (possibly
others) as unicode?
This seems like a bug, possibly overlooked, but having unicode keys
prevents certain functionality like **request.GET in a method call.
--~--~-~--~~~---~--~~
You received
On 12.07.2007., at 00:16, Marc Garcia wrote:
> I've checked translation module on django-utils, and django-
> multilingual, and both solve the problem, but I want a more intuitive
> way for end-users (who fill data in admin).
Main problem (which django-multilingual tries to solve) how to define
www.OutpatientSurgicare.com/video/
Outpatient Doctors Surgery Center is committed to offering the
healthcare the community needs. We offer patients a meaningful
alternative to traditional surgery. This state-of-the-art outpatient
surgery center, located in the heart of Orange County, at 10900
James Bennett wrote:
> On 7/11/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
>> This sounds like a strange way to ask if Django is using prepared
>> statements[1] or their equivalents, rather than simply supplying
>> values directly within the SQL statement itself. To my knowledge,
>> Django
On Jul 11, 6:16 pm, Marc Garcia <[EMAIL PROTECTED]> wrote:
> I've designed an admin page with my
> idea:http://vaig.be/2007/07/11/django-database-texts-translated/
I link this Idea a lot in principal and think it would be easier to
maintain than other solutions I have seen (at first blush).
I
On 7/11/07, Marc Garcia <[EMAIL PROTECTED]> wrote:
> I haven't seen any post or any ticket that anybody that is working on
> something like that. If anybody does, please let me know.
Check out django-multilingual[1] and its documentation[2]. I can't
guarantee this is exactly what you're looking
On 7/11/07, James Bennett <[EMAIL PROTECTED]> wrote:
> No, the question here is whether Django is calling cursor.execute()
> with an empty params list or with a non-empty params list (the answer
> is: the latter, in most cases). Prepared statements are something else
> entirely, and should not be
On 11.07.2007., at 19:27, David Cramer wrote:
> That's an interesting solution. My main reason for not doing that is
> because I've been told the dispatcher sucks (it's slow) and we're
> going for speed.
Using CachedModel as a base class will be ideal, but ... this will
not work until model
Hi,
(was
http://groups.google.com/group/django-developers/browse_thread/thread/1695343f1e5cdc36/f4918ceac3a2f246)
I answer myself since I have submitted a new patch[1] that behaves
like Adrian suggested it:
# Model
class Book(models.Model):
title = models.CharField(maxlength=100)
author
Hi all!
I've been searching for a way to create a multilingual catalog with
django, and there is just one thing missing, a simple way for
translating information on database, for example having product
description in more than one language.
I've checked translation module on django-utils, and
This snippit replaces the request.path. My question is, how does this
work with sitemap, absolute rul's and reverse url lookups? doesn't it
break all of those, or am I missing something?
-Doug
--~--~-~--~~~---~--~~
You received this message because you are
Keeping the tutorial documentation working should be paramount.
http://code.djangoproject.com/ticket/4615 has been waiting for checkin
for a while. Could a committer please review it?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Marty Alchin wrote:
> On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>> What is djagoo's approach to passing values to the back end:
>>
>> A) create a string that is the SQL command and the values, pass that string
>> to
>> the db module.
>>
>> B) create a string that is the SQL command
On 7/11/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> This sounds like a strange way to ask if Django is using prepared
> statements[1] or their equivalents, rather than simply supplying
> values directly within the SQL statement itself. To my knowledge,
> Django doesn't support them, and I
This really isn't meant to compete with Django, more with SQLAlchemy.
So far it seems like it's main competing feature is handling
multiple-databases easily and joining across them.
Damien Gassart saw these posts on digg, made by zzzeek and niemeyer,
the SQLAlchemy and Storm lead developers,
Hi guys,
Check out http://www.djangosnippets.org/snippets/307/
I think it's best solution for this problem. I'm already happy.
Looking forward to including this in django itself.
On Tue, 2007-07-10 at 23:45 +, Graham Dumpleton wrote:
[...]
> Django has problems in related areas with CGI and
On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
> What is djagoo's approach to passing values to the back end:
>
> A) create a string that is the SQL command and the values, pass that string to
> the db module.
>
> B) create a string that is the SQL command with parameter markers, pass that
>
On 7/11/07, David Cramer <[EMAIL PROTECTED]> wrote:
>
> That's an interesting solution. My main reason for not doing that is
> because I've been told the dispatcher sucks (it's slow) and we're
> going for speed.
>
> I don't see the reasoning for adding QUERY_ to the cache_key. By
> default the
Jacob Kaplan-Moss wrote:
> On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>> What is djagoo's approach to passing values to the back end:
>
> Django builds on the standard Python DB-API (aka PEP 249:
> http://www.python.org/dev/peps/pep-0249/). Read that PEP for the
> details.
That did not
On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
> What is djagoo's approach to passing values to the back end:
Django builds on the standard Python DB-API (aka PEP 249:
http://www.python.org/dev/peps/pep-0249/). Read that PEP for the
details.
Jacob
> Just an idea: decorators for strings could also be implemented.
>
> url(r'regex', 'project.app.views.myview', decorator=login_required)
>
> Pistahh
-1
What happens when you need multiple stacked decorators? Decorators
which require arguments (auth_required) which might be complex would
mean
Anyone? I've seen at least two threads related to this subject; I know
I'm not the only one wondering.
Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
Hi Adrian,
Thank you for the quick reply. I have opened a ticket; we'll see what
happens.
http://code.djangoproject.com/ticket/4848
Thank you for all of your hard work! I'm really enjoying getting to
know Django.
Cheers,
Leif
--~--~-~--~~~---~--~~
You
I have not dug into the code much, but I did find this:
def get_db_prep_save(self, value):
# Casts dates into string format for entry into database.
if value is not None:
value = value.strftime('%Y-%m-%d')
return Field.get_db_prep_save(self, value)
Ya some of the stuff seems like a bit of extra work. I really like how
they handle the objects in memory though so they're referencable
before saving in the database, even with ForeignKeys. Although our
Django is patched, the current trunk doesn't even store multiple
references to the same object
That's an interesting solution. My main reason for not doing that is
because I've been told the dispatcher sucks (it's slow) and we're
going for speed.
I don't see the reasoning for adding QUERY_ to the cache_key. By
default the cache_key is your db_table. So if your model is
myapp.HelloWorld it
James Bennett wrote:
> On the other hand, importing the functions and using them directly
> opens up some interesting possibilities -- you can apply decorators
> like 'login_required' to them right there in the URLConf, which adds
> another layer of configurability that isn't possible when
On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 7/11/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
> > Also, it might be worth the project's time to pick a distributed VCS
> > and host mirrors on djangoproject.com.
>
> Tom's Mercurial mirror is basically the official DVCS version of
On Wed, Jul 11, 2007 at 09:38:54AM -0500, Deryck Hodge wrote:
>
> On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> > The best thing to do is host your changes remotely. That way there's
> > no implicit assumptions about if and when it'll get merged into
> > Django.
> >
>
> Hi, Jacob.
>
On 7/11/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
> Also, it might be worth the project's time to pick a distributed VCS
> and host mirrors on djangoproject.com.
Tom's Mercurial mirror is basically the official DVCS version of
Django; if it gets popular at all we'll probably move it onto
On 11.07.2007., at 14:25, Nebojša Đorđević wrote:
> Full code is at http://dpaste.com/hold/14105/
Here is my final take on this problem: http://dpaste.com/hold/14122/
I changed caching so that all of the queries related to the one model
are stored inside single cache key. This way I can
On 11 jul, 00:09, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
>
> Can you help out a little bit here by providing a test case (not
> necessarily a unit test - just a clear set of instructions for how to
> generate they type of error that your patch proposes to catch? I can
> see the general
On Wed, Jul 11, 2007 at 09:43:15PM +0700, Ben Ford wrote:
> I'm already happily using SVK, and was originally planning to use it to
> remotely host the multi-db branch on my virtual server... However the only
> info
> I could find on achieving this was incorrect and I'm not sure if it is even
>
Forest,
I'm already happily using SVK, and was originally planning to use it to
remotely host the multi-db branch on my virtual server... However the only
info I could find on achieving this was incorrect and I'm not sure if it is
even possible to split repos (onto 2 different machine), which is
On 7/11/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
> > Any feedback (especially objections to committing) would be
> > appreciated.
>
> First, great work! I think all the kiddies will like it. Won't be long
> before Django has a Scriptaculous widget set, I bet :)
On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> The best thing to do is host your changes remotely. That way there's
> no implicit assumptions about if and when it'll get merged into
> Django.
>
Hi, Jacob.
I'll mention Bazaar, too. My experience with it has been very pleasant.
I
Hi Guys
I have added a patch to Ticket #399 at:
http://code.djangoproject.com/attachment/ticket/399/django-bigint-20070711.patch
It should implement BigIntegerField for all django backends, although I have
only tested against sqlite and postgresql. (The others are correct according
On Wed, Jul 11, 2007 at 09:12:14AM -0500, Jacob Kaplan-Moss wrote:
> Probably the best way to host an "unofficial" branch would be by using
> Tom's Mercurial mirror of Django trunk:
> http://hg.korpios.com/django.trunk/.
Since you're on svn, you might also try svk.
-Forest
signature.asc
On 7/11/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> None as yet, I'm really keen to get it back into the svn repo, but I think
> the people concerned are busy with other things at the moment.
I've said this a couple times, but I guess it's been missed:
We're moving away from giving branch access
Peter,
I ran into this problem when I was bringing the multi-db branch up to date
and was so busy I forgot to tell anyone! (My bad) I fixed it, but it was on
another machine. It's a pretty simple change, but the exact diff escapes me
at the moment! Is there a ticket on this, as I think it might be
On Wed 11 Jul 2007, Michael Radziej wrote:
> Hi,
>
> you're using the alpha version of SuSE ... well ... there might very well
> be a problem very deep in one of the libraries. The alpha releases aren't
> very reliable. I'd suggest that you try it with another OS.
Hi Michael
While I agree that
When running "python manage.py inspectdb" against the following postgresql
table:
# \d auth_message
Table "public.auth_message"
Column | Type | Modifiers
-+-+---
id
This is a rough version of our cache invalidator, including a sample
decorator and a cached template tag:
http://dpaste.com/14107/
If you have multiple web servers talking to one cache (which is our
case) you can use some message passing system (like activeMQ) to
propagate the signals to other
On Wed 11 Jul 2007, David Danier wrote:
> > Basically django simply exists whenever it gets data based from
> > postgresql.. anywhere. syncdb, inspecdb, /admin/ and everything else
> > that access the db simple die/exit with an "Aborted" message..
>
> As the changeset mentioned earlier was the
On 09.07.2007., at 01:11, David Cramer wrote:
> Here's about as final as we're going to get it for now: http://
> dpaste.com/hold/13884/
Great work :)
About cache invalidation ... why you can use something like this
http://dpaste.com/hold/14104/
and just add:
class Foo(models.Model):
> Basically django simply exists whenever it gets data based from postgresql..
> anywhere. syncdb, inspecdb, /admin/ and everything else that access the db
> simple die/exit with an "Aborted" message..
As the changeset mentioned earlier was the unicode-merge:
Is the datebase-encoding set to
Yesterday I saw this bug as well when working with a new project and Django
trunk. For me it went away when I changed settings.py from:
DATABASE_ENGINE = 'postgresql_psycopg2'
to
DATABASE_ENGINE = 'postgresql'
Regards,
Marijn Vriens.
On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
>
>
>
Hi Paul
The problem was described (as much as it is possible to) in the initial mail
to the users list as well as below in the test requested by Russell.
Basically django simply exists whenever it gets data based from postgresql..
anywhere. syncdb, inspecdb, /admin/ and everything else that
Peter,
I may be blind, but I can't see anywhere you've actually specified what the
bug is. What behaviour is exhibited?
On 7/11/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
>
>
> Cross posted to -devel as this is definitely a bug
>
> On Wed 11 Jul 2007, Peter Nixon wrote:
> > On Wed 11 Jul
Cross posted to -devel as this is definitely a bug
On Wed 11 Jul 2007, Peter Nixon wrote:
> On Wed 11 Jul 2007, Russell Keith-Magee wrote:
> > On 7/10/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> > > How can I debug this in a way that will provide the developers with
> > > more usefull info?
Hi,
None as yet, I'm really keen to get it back into the svn repo, but I think
the people concerned are busy with other things at the moment. I can send
you the patch if you like and I'll chase them up again.
Ben
On 11/07/07, koenb <[EMAIL PROTECTED]> wrote:
>
>
> Is there any news on updating
I am trying to create a django backend for DB2. I am trying to do this
using a DB2 Express C and the pydb2 module.
It is coming around quite nicely. I have the test suite down to 7
failures and 3 errors, but now I am a bit stuck.
My biggest hurdle at this point is that DB2 does not have an easy
Is there any news on updating the svn repo for this branch ?
k
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To
Malcolm Tredinnick wrote:
> On Tue, 2007-07-10 at 09:20 +0200, Gábor Farkas wrote:
>> hi,
>
>> i'm always using the "pythonic" way (import the view function, and give
>> it to the urlconf), and assumed that this is the recommended way.
>>
>> but what always worried me is that you still have to
68 matches
Mail list logo
