Re: Upcoming Django release, and the future
On Tuesday, February 27, 2007, 8:41:44 AM, Marc Fargas Esteve wrote: > Hi Andrew, > There's a ticket for that openned: > http://code.djangoproject.com/ticket/3589 > And it's closed as fixed :) Thanks! The ticket itself doesn't have 'postgresql_psycopg2' in it, so I didn't find it searching. And it was fixed since my last svn checkout. -- Best regards, Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Upcoming Django release, and the future
On Monday, February 26, 2007, 4:39:29 PM, James Bennett wrote: > On 2/26/07, Andrew Diederich <[EMAIL PROTECTED]> wrote: >> On Monday, February 26, 2007, 3:00:30 PM, Jacob Kaplan-Moss wrote: >> > For the other bit, though, see [4624]. >> >> This ticket doesn't exist. I looked for similarly numbered ones, but >> didn't find it. > That's changeset 4624, not ticket 4624: > http://code.djangoproject.com/changeset/4624 Whoops -- I knew about the #ticketnumber searching in trac, but not the [changeset] shortcut. Thanks. This changeset just applies to the install.txt file. Is there one that changes the generated settings.py file? By default it's something like: DATABASE_ENGINE = '' # 'postgresql', 'mysql', 'sqlite3' or 'ado_mssql'. and it'd be better if it also specified postgresql_psycopg2 as well. I'm happy to log a ticket if that's the best way to get it recorded and included. -- Best regards, Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re[2]: Upcoming Django release, and the future
On Monday, February 26, 2007, 3:00:30 PM, Jacob Kaplan-Moss wrote: > On 2/26/07, Andrew Diederich <[EMAIL PROTECTED]> wrote: >> I'd like to see the mssql patches applied, ticket >> http://code.djangoproject.com/ticket/2358. I'd also like to see the >> postgresql_psycopg2 database option mentioned in the default comments >> in the settings.py file for the DATABASE_ENGINE setting. > MSSQL, unfortunately, will likely need to wait until after Malcolm > does his QuerySet refactoring (otherwise the code's just too > difficult). That's too bad. I have the patches in #2358, at least, to keep me going for now, which is good. > For the other bit, though, see [4624]. This ticket doesn't exist. I looked for similarly numbered ones, but didn't find it. -- Best regards, Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Upcoming Django release, and the future
On Sunday, February 25, 2007, 9:56:36 PM, James Bennett wrote: > If you've got any questions about all of this, feel free to reply and > I'll do my best to answer them or delegate to someone who can. And if > you've got some free time this week and want to help us kill bugs in > the run up to 0.96, let us know and we'll be happy to show you how you > can help. I'd like to see the mssql patches applied, ticket http://code.djangoproject.com/ticket/2358. I'd also like to see the postgresql_psycopg2 database option mentioned in the default comments in the settings.py file for the DATABASE_ENGINE setting. -- Best regards, Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Using __str__ with DateField
On 2/10/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 2/10/07, Andrew Diederich <[EMAIL PROTECTED]> wrote: > > Is there an easy way to munge the return self.end_date into a string? > > This is a Python requirement -- __str__() methods must return a > string. To fix the problem, wrap self.end_date in str(), like so: > > return str(self.end_date) Perfect. I thought it would be intensely easy. Thanks for the help. -- Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Using __str__ with DateField
I'm setting up a simple timecard app as a django proof-of-concept.
One of my models is "Period" that specifies the end-date of the time
period (usually a Friday).
I'm not getting __repr__ right.
Trying to add a period in the admin side:
TypeError at /admin/timekeeper/period/add/
__str__ returned non-string (type datetime.date)Request Method: POST
Request URL:http://localhost:8000/admin/timekeeper/period/add/
Exception Type: TypeError
Exception Value:__str__ returned non-string (type datetime.date)
Exception Location:
c:\python25\lib\site-packages\django\contrib\admin\views\main.py
in add_stage, line 256
The model:
class Period(models.Model):
end_date = models.DateField('end date')
insert_date = models.DateTimeField('date inserted', auto_now_add=True)
def __str__(self):
return self.end_date
class Admin:
pass
Is there an easy way to munge the return self.end_date into a string?
Thanks for the help.
--
Andrew Diederich
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: New Vim files for Django
On Sunday, January 28, 2007, 9:54:18 AM, Dave Hodder wrote: > Updated syntax files for the Vim editor are available here: > http://www.vim.org/scripts/script.php?script_id=1487 Is the htmldjango.vim 1.05 version the right one to grab? i.e. are they all supposed to do the same thing, and that one is the latest? -- Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Tools for writing HTML templates
On 1/27/07, Paulo <[EMAIL PROTECTED]> wrote: > > This could turn into a religious debate... but I give TextMate two thumbs up! > > < http://macromates.com/ > TextMate looks nice, but I don't have a mac. We've primarily been a windows shop, with a handful of linux and solaris servers. Have you run into anything your windows friends like? Another category of user I'm looking for is me. Decidedly non-graphical, not a python wunderkind, just looking for something to lay out simple pages for testing, developing django ideas, and so on. -- Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Tools for writing HTML templates
I'm looking for a tool for our non-programmers to develop the HTML templates for django. Our python folks can help stick in the template code, but the folks we have to make the website good-looking aren't necessarily the same people. Are there any HTML editing tools that people here have enjoyed using for making hte HTML and CSS needed to make a good looking django site? Nvu? Homesite? -- Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re[2]: inspectdb support for ado_mssql?
Hello Sean, On Wednesday, January 24, 2007, 8:14:11 AM, Sean De La Torre wrote: > Look at this ticket: http://code.djangoproject.com/ticket/2358. More > specifically, use the mssql_update5.diff file - I'm don't think the > anonymously contributed patch after that actually does much. > I haven't updated it to the latest SVN because of a lack of time, but > it shouldn't be too hard to figure out in case there are conflicts. That worked reasonably well. One bit of the diff didn't go cleanly, but I flailed around in tortoiseSVN until the error went away. I was able to do inspectdb. Thanks for the help. -- Best regards, Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
inspectdb support for ado_mssql?
Has anyone been able to get inspectdb working for 0.96-dev (svn) django? I just got my connect string working (non-standard port issue), but at first go it looks like inspectdb isn't yet supported for ado_mssql, which is too bad. Here's what happens when I run it: C:\eggs>django-admin.py inspectdb --settings=myapp.settings # This is an auto-generated Django model module. # You'll have to do the following manually to clean this up: # * Rearrange models' order # * Make sure each model has one field with primary_key=True # Feel free to rename the models, but don't rename db_table values or field name s. # # Also note: You'll have to insert the output of 'django-admin.py sqlinitialdata [appname]' # into your database. from django.db import models Error: 'inspectdb' isn't supported for the currently selected database backend. introspection.py for ado_mssql has NotImplementedError in all the classes, so I may be just out of luck on this one. -- Andrew Diederich --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Connection error with ado_mssql
I'm trying to connect 0.96-dev out of svn to a sql2k server, running
with a named instance. I've seen that the connection string django
uses has a different style than what I've used with adodbapi before.
I've tried replicating the django connection string in a python
prompt, but that failed, too.
Has anyone else been able to get around similar errors? Here's what I
get from django/python:
C:\eggs>django-admin.py inspectdb --settings=myapp.settings
Traceback (most recent call last):
File "c:\python24\scripts\django-admin.py", line 5, in ?
management.execute_from_command_line()
File "C:\Python24\lib\site-packages\django\core\management.py", line 1358, in
execute_from_command_line
for line in action_mapping[action]():
File "C:\Python24\lib\site-packages\django\core\management.py", line 747, in i
nspectdb
cursor = connection.cursor()
File "C:\Python24\lib\site-packages\django\db\backends\ado_mssql\base.py", lin
e 72, in cursor
self.connection = Database.connect(conn_string)
File "C:\Python24\lib\site-packages\adodbapi\adodbapi.py", line 224, in connec
t
raise DatabaseError(e)
adodbapi.adodbapi.DatabaseError: (-2147352567, 'Exception occurred.', (0, 'Micro
soft OLE DB Provider for SQL Server', '[DBNETLIB][ConnectionOpen (Connect()).]SQ
L Server does not exist or access denied.', None, 0, -2147467259), None)
The database does exist, and I've been able to connect to it with
Query Analyzer with the login, password, and server name I used in my
config file. This is how django makes the connection:
conn_string = "PROVIDER=SQLOLEDB;DATA
SOURCE=%s;UID=%s;PWD=%s;DATABASE=%s" % (settings.DATABASE_HOST,
settings.DATABASE_USER, settings.DATABASE_PASSWORD,
settings.DATABASE_NAME)
self.connection = Database.connect(conn_string)
Here is how I've done it in the past:
>>> conn = adodbapi.connect('Driver={SQL
Server};Server=theServer,1533;Initial Catalog=theDatabase;User
ID=theUser;Password=thePassword;')
Do I need a DSN to make the connection?
[Time passes]
Ok, figured it out. Since I've already put in the text, I'll write up
the answer so google gets smarter. My db is on a non-standard port,
and that isn't picked up correctly in base.py yet. So, the
work-around is to name the server SERVER,PORT in the settings file.
Like this:
DATABASE_HOST = 'dbServerName,1733'
And it now connects!
--
Andrew Diederich
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
