Ok, turns out when I set TIME_OUT to 'UTC' it was storing and
retrieving the dates correctly. But when I was viewing the dates in
psql and pgAdmin III it was showing the dates using my system's time
zone data.
--
You received this message because you are subscribed to the Google Groups
"Django
Not only do I have settings.TIME_ZONE set to 'UTC', I'm also creating
datetime objects via utcfromtimestamp() as follows:
field = datetime.datetime.utcfromtimestamp(time.time())
So I figured they would be going into the database as UTC anyway.
When I figured out that they were showing UTC-6 i
On Dec 6, 9:21 pm, Graham Dumpleton
wrote:
> Some explanation of this issue in:
>
> http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Timezone_and_...
>
> If using Apache/mod_wsgi, delegate Python web application instances
> with specific timezone, locale, lang requirements to a separate
On Dec 6, 8:39 pm, Brian Neal wrote:
> What is your server setup? Apache on Linux? mod_python or mod_wsgi?
> Are you running anything else on your server like PHP apps? The
> timezone setting is process-wide, so depending on how you deployed
> your server another application could be overwriting
I've changed settings.TIME_ZONE to 'UTC' and restarted my server but
when I create records (postgresql) they're not UTC, they're 'America/
Chicago' (-6) in the table.
Am I missing something or is settings.TIME_ZONE useless?
--
You received this message because you are subscribed to the Google Gr
I'm working with a table of objects where all the objects have a
unique rank value. When I add an object I need to query the table to
get the last object in the rank index, then apply an incremented value
to the new object to effectively put it last in the rank order. I
need to eliminate the p
Yeah, apparently I needed the admin templates in a previous version.
I renamed templates/admin and it's all good now. Thanks!
On Aug 28, 8:10 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 8:56 PM, XtraGreen <[EMAIL PROTECTED]> wrote:
>
I'm upgrading a Django site from 0.96 to the 1.0 beta (django-trunk
svn as of tonight) and it's mostly going smoothly except the built in
Django admin is giving me issues.
I think I've got everything setup for the new admin code, but when I
try to execute the main admin page I get the following e
8 matches
Mail list logo
