On 4/22/07, Florian Apolloner <[EMAIL PROTECTED]> wrote:
> I would like to be able to do something like this:
> http://groups.google.at/group/django-users/browse_thread/thread/62ef2b417fad1b8d/532c9b3fdf2ad36d
>
> Any chance to get this into the new admin?
Please keep in mind when suggesting feat
On Sun, 2007-04-22 at 20:28 +, Fraser Nevett wrote:
> Hi All,
>
> I'm sure I'm not alone in using simple print statements to trace/log
> what is going on in a Django app, especially when debugging. This
> works OK when using runserver, but can be more difficult and
> problematic to use with m
Hi,
I have been using the Oracle branch now for a few months and it is
looking really good.
I have a question regarding the use of the 'db_tablespace' option in
the Meta class. I am able to set this option within my application and
successfully perform a syncdb that will place all my tables in t
On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I downloaded the patch and got it to work. I have a couple of
> observations based on usage.
>
> - If we continue to use the format "150x200" to specify the size, we
> may want to do a string.lower() on the input. I originally had a
>
I downloaded the patch and got it to work. I have a couple of
observations based on usage.
- If we continue to use the format "150x200" to specify the size, we
may want to do a string.lower() on the input. I originally had a
capital X and couldn't figure out what the problem was. Yeah, it's a
On 4/22/07, Fraser Nevett <[EMAIL PROTECTED]> wrote:
...
> I'm sure I'm not alone in using simple print statements to trace/log
Huzzah, you've knocked something off my to-do list. :)
I've read the doc but not yet the code. My immediate feedback is that
it'd be nice to have a convention of
logg
On 4/22/07, John Calixto <[EMAIL PROTECTED]> wrote:
...>
> I presume, if developer A had already applied the first couple
> migrations to their testdb, they'd do something like:
>
> migration_list = [
> # 'migration1',
> # 'migration2',
> 'migration3',
> 'migrat
MikeH wrote:
> Hi all,
>
> I'm currently preparing my team to use Django as our primary framework
> and as part of this we need a way to keep our databases in sync.
>
>>From the Django FAQ:
>> you'll have to execute the ALTER TABLE statements manually in your database.
>> That's the way we've al
On Apr 23, 9:25 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> This is a really great patch. I read the patch but have not attempted
> to use yet. Here are a couple of thoughts:
> - I think the patch file itself may be a little messed up. I see that
> several of the files are repeated. I
On Apr 22, 2:42 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Yes, it would work. Why is it necessary to introduce the complexity (and
> risk of screwing it up), though? We have the default attribute on models
> for this type of thing. You're really leaking abstractions here.
I'm not saying
This is a really great patch. I read the patch but have not attempted
to use yet. Here are a couple of thoughts:
- I think the patch file itself may be a little messed up. I see that
several of the files are repeated. I could just be reading it wrong.
- Big positive in that you documented it s
> Just use datetime.now without the function call parentheses.
Know this, doesn't work for newforms (initial value).
I added a ticket (including a patch) to fix this:
http://code.djangoproject.com/ticket/4018
David
--~--~-~--~~~---~--~~
You received this message
Hi All,
I'm sure I'm not alone in using simple print statements to trace/log
what is going on in a Django app, especially when debugging. This
works OK when using runserver, but can be more difficult and
problematic to use with mod_python in a production environment.
To try to give greater contr
2007/4/22, Honza Král <[EMAIL PROTECTED]>:
>
> try to use the cache manually from the shell, if its cache related, or
> the decorator is at fault
>
It has been an Argh! issue :)
I use CACHE_MIDDLEWARE_ANONYMOUS_ONLY to not cache admin and private
pages. But if you use that it doesn't caché public
On 4/22/07, aaloy <[EMAIL PROTECTED]> wrote:
>
> 2007/4/22, Honza Kr�l <[EMAIL PROTECTED]>:
> > On 4/22/07, aaloy <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello All!
> > Hello,
> >
> > >
> > > I have a view like
> > >
> > > def record(request, id, type):
> > > # some database code here
> > > # some
2007/4/22, Honza Král <[EMAIL PROTECTED]>:
> On 4/22/07, aaloy <[EMAIL PROTECTED]> wrote:
> >
> > Hello All!
> Hello,
>
> >
> > I have a view like
> >
> > def record(request, id, type):
> > # some database code here
> > # some log code here
> > record=cache_page(record,60)
> >
> > If I have corr
On 4/22/07, aaloy <[EMAIL PROTECTED]> wrote:
>
> Hello All!
Hello,
>
> I have a view like
>
> def record(request, id, type):
> # some database code here
> # some log code here
> record=cache_page(record,60)
>
> If I have correctly understood the documentation, if I maque a request
> to that view
Hello All!
I have a view like
def record(request, id, type):
# some database code here
# some log code here
record=cache_page(record,60)
If I have correctly understood the documentation, if I maque a request
to that view with the same parameters the view shoud'nt hit the
database neither get
Just use datetime.now without the function call parentheses.
See
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RemovedLazyDate
for an explanation.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"
On Sat, 2007-04-21 at 23:55 -0700, ~Kender wrote:
> Along this same line, there's another issue with the RadioSelect
> widget.. It makes use of a rendering (returned by the render method)
> but the class is hardcoded in the method, so there's no way to supply
> an alternative renderer except to su
On Sun, 2007-04-22 at 06:56 +, Collin Grady wrote:
> On Apr 21, 9:53 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
> > Your database may still have a serial value
> > on that field, for example, or there may be a trigger that does the
> > value computation. Both of these are a little unr
I put together my take on django.contib.thumbnails and posted it as a
patch
http://code.djangoproject.com/ticket/4115
Please read through the documentation and give some feedback.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
I would like to be able to do something like this:
http://groups.google.at/group/django-users/browse_thread/thread/62ef2b417fad1b8d/532c9b3fdf2ad36d
Any chance to get this into the new admin?
Thx, Florian
--~--~-~--~~~---~--~~
You received this message because y
23 matches
Mail list logo
