headers
mugdiman@googlemail.com | 1 Aug 2007 01:39

Re: Dojo LayoutContainer and ContentPane as application frame?


ok the solution was

dojo.io.bind({
url: "/projects/",
load: function(type, data, evt){ docPane.setContent(data); },
mimetype: "text/html"
});

sorry ...

On 31 Jul., 22:37, "mugdi... <at> googlemail.com" <mugdi... <at> googlemail.com>
wrote:
> Hello Group,
>
> I tried to setup a kind of frame architecture with the dojo layout
> container widget.
> The idea is to load the menu (fisheye widget menu) only once and let
> the django page itself load asynchronously into a ContentPane.
> A dojo menu widget loads an url in the content pane like this:
>
>         function load_app(id){
>                 var docPane = dojo.widget.byId("docpane");
>                 if (id == 6) {
>                         docPane.setUrl("/projects/");
>                 }
>         }
>
> Projects is an application of my site. The main urls.py includes the
> url of the projects application:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Greg | 1 Aug 2007 01:48
Picon
Favicon

Re: Error: 'unicode' object has no attribute 'strftime'. Just added models.DateField


bump

On Jul 31, 2:53 pm, Greg <gms3... <at> hotmail.com> wrote:
> Russ,
> Ha...sorry I'm such a idiot.
>
> I think I got in now (If not...you might need to help me find it).
>
> My Zip file that I downloaded is labeled sqlite-3_3_15.  Is that what
> you need?
>
> Sorry about this confusion Russ
>
> Thanks
>
> On Jul 31, 9:10 am, "Russell Keith-Magee" <freakboy3... <at> gmail.com>
> wrote:
>
> > On 7/31/07, Greg <gms3... <at> hotmail.com> wrote:
>
> > > pysqlite2.3.3
>
> > That's just the binding. What version of SQLite itself?
>
> > Russ %-)

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
bradford.mcgonigle@gmail.com | 1 Aug 2007 02:05
Picon

Re: Flickr / Django


Bret,

Your model and sync script looks exactly like what I was starting to
write!!  Heck yeah!

Anyway, I have everything set up but I keep getting this error and I'm
not 100% sure why....

Traceback (most recent call last):
  File "flickr/flickrupdate.py", line 7, in <module>
    from models import Photo
  File "/home2/spyderfcs/webapps/django/bradmcgonigle/flickr/
models.py", line 1, in <module>
    from django.db import models
  File "/home2/spyderfcs/lib/python2.5/django/db/__init__.py", line 7,
in <module>
    if not settings.DATABASE_ENGINE:
  File "/home2/spyderfcs/lib/python2.5/django/conf/__init__.py", line
28, in __getattr__
    self._import_settings()
  File "/home2/spyderfcs/lib/python2.5/django/conf/__init__.py", line
53, in _import_settings
    raise EnvironmentError, "Environment variable %s is undefined." %
ENVIRONMENT_VARIABLE
EnvironmentError: Environment variable DJANGO_SETTINGS_MODULE is
undefined.

On Jun 29, 5:06 pm, "bretwal... <at> gmail.com" <bretwal... <at> gmail.com>
wrote:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Patrick Anderson | 1 Aug 2007 02:14
Picon

Re: User model (unique email)


On Tue, 31 Jul 2007 22:40:50 +0000, Pensee wrote:

> Hi,
> 
> On Jul 31, 11:46 pm, Patrick Anderson <pat.j.ander... <at> gmail.com> wrote:
>> I'd prefer not to hack the contrib.auth application and change User
>> model,
> 
> Adding just unique=true is not so hard and tracking with changes is easy
> :).
> 
> You may have a look at the "Django tips: extending the User model" on
> The B List [1]
> 
>> so perhaps that constraint should be included in my application code,
>> but I'm not sure what the best way to do it should be.
> 
> I think that's a bit of too much overhead. I mean you already have a
> bunch of code that can handle this automaticaly.
> 
> -- Amirouche
> 
> 
> 
True, that is probably the least complicated method, but it requires me 
to remember this little hack.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
(Continue reading)

Permalink | Reply | 0 comments |
headers
James Bennett | 1 Aug 2007 02:17
Picon

Re: Flickr / Django


On 7/31/07, bradford.mcgonigle <at> gmail.com <bradford.mcgonigle <at> gmail.com> wrote:
> Your model and sync script looks exactly like what I was starting to
> write!!  Heck yeah!

There's also an open-source app which aims to genericize the function
of periodically pulling in some form of external content to your
database, and which includes "providers" (pluggable modules for
importing data) for Flickr and other services:

http://code.google.com/p/jellyroll/

--

-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
Kevin Menard | 1 Aug 2007 02:38
Picon
Gravatar

Re: Unique check errors when using postgres and explicit ids


On 7/31/07, Kai Kuehne <kai.kuehne <at> gmail.com> wrote:
>
> Hi list,
> I have a question regarding data imports with django
> and postgres.
> I used the database for my current application and used
> the db-dump script from here:
> http://www.djangosnippets.org/snippets/14/
>
> When I load data into the database, I cannot insert new
> data afterwards. (Some weird unique check errors.)

I would have to agree with lenducha's synopsis.  If the sequence is
not updated, you will run into duplicate ID problems.  The easiest
thing to do right now is update all of your sequence curvals to be
something large, where large is defined as being greater than count(*)
for each table.

--

-- 
Kevin

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hai Dong | 1 Aug 2007 02:46
Picon

a question about site framework


Hello:

I got a question. What if I have two sites, and each site has several
categories (where articles belong to). For such kind of case what is the
best way of utilizing the site framework.

Thanks,
Harry

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 5 comments |
headers
Russell Keith-Magee | 1 Aug 2007 02:50
Picon
Gravatar

Re: Unique check errors when using postgres and explicit ids


On 8/1/07, Kai Kuehne <kai.kuehne <at> gmail.com> wrote:

> I'm using django SVN and the windows version of psycopg2.
> Postgres is running on linux (version 8.1.8). It doesn't work on
> webfaction either, so this information shouldn't be that helpful.

Without seeing the exact error, I can think of two possible causes:

- MySQL is hiding some key-referential integrity problems that
Postgres is revealing. MySQL MyISAM tables don't check referential
integrity, so if you have forward references in your data, Postgres
could be choking where MySQL won't.

- You need to reset your Posgres sequences. './manage.py
sqlsequencereset' will generate the SQL code that will fix the
problem; this will reset the primary key sequences and allow you to
add new objects.

I should also point out that this problem doesn't exist with the
database dump mechanism that is built into Django. ./manage.py
loaddata automatically does a sequence reset after loadin a fixture.

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
(Continue reading)

Permalink | Reply | 3 comments |
headers
Kai Kuehne | 1 Aug 2007 02:50
Picon

Re: Unique check errors when using postgres and explicit ids


On 8/1/07, Kevin Menard <nirvdrum <at> gmail.com> wrote:
> I would have to agree with lenducha's synopsis.  If the sequence is
> not updated, you will run into duplicate ID problems.  The easiest
> thing to do right now is update all of your sequence curvals to be
> something large, where large is defined as being greater than count(*)
> for each table.

I'm not sure whether this is a problem of the script, psycopg2
or postgres. Things work with mysql so I have to stick with
that in the near future.

> --
> Kevin

Thanks for answering
Kai

--~--~---------~--~----~------------~-------~--~----~
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 <at> googlegroups.com
To unsubscribe from this group, send email to django-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Kai Kuehne | 1 Aug 2007 03:05
Picon

Re: Unique check errors when using postgres and explicit ids


Hi Russell

On 8/1/07, Russell Keith-Magee <freakboy3742 <at> gmail.com> wrote:
>
> On 8/1/07, Kai Kuehne <kai.kuehne <at> gmail.com> wrote:
>
> > I'm using django SVN and the windows version of psycopg2.
> > Postgres is running on linux (version 8.1.8). It doesn't work on
> > webfaction either, so this information shouldn't be that helpful.
>
> Without seeing the exact error, I can think of two possible causes:
>
> - MySQL is hiding some key-referential integrity problems that
> Postgres is revealing. MySQL MyISAM tables don't check referential
> integrity, so if you have forward references in your data, Postgres
> could be choking where MySQL won't.

I know, it sounds weird.. but there are no integrity problems in the database.
If there were problems, I think I should see them popping up in pgadmin.
I can be wrong, though.

> - You need to reset your Posgres sequences. './manage.py
> sqlsequencereset' will generate the SQL code that will fix the
> problem; this will reset the primary key sequences and allow you to
> add new objects.

Is this the 'normal' behavior of postgres? I've never used it
before but this seems very odd to me. I'm deleting the whole
database and creating it new every time. After deleting I'm doing this:
(Continue reading)

Permalink | Reply | 2 comments |

Gmane