On Dec 29, 2005, at 10:06 PM, Tom Tobin wrote:
On 12/29/05, David Pratt <[EMAIL PROTECTED]> wrote:
Doesn't Swish-e pose an incompatibility for licensing? Everything
Django
has been BSD up to this point and I would hate to see anything alter
this. Isn't swish-e gpl?
Swish-e grants a special
On Friday 30 Dec 2005 12:39 am, Jarek Zgoda wrote:
> - the whole ORM-thingy should be split into separate section, as
> it defines the crucial part of application (you can change views
> and controllers in your application, but not the model); the data
> is your customer's treasure.
there is
On Friday 30 Dec 2005 5:12 am, hugo wrote:
> So, yes, I do think it would be very useful for Django to be able
> to access multiple databases via it's ORM
incidently, we need support for postgres schemas also - i have an
Financial Accounting app where, in multi-company mode, the tables
for
On 12/29/05, David Pratt <[EMAIL PROTECTED]> wrote:
>
> Doesn't Swish-e pose an incompatibility for licensing? Everything Django
> has been BSD up to this point and I would hate to see anything alter
> this. Isn't swish-e gpl?
Swish-e grants a special exemption from automatically GPL'ing linked
Hi Jacob and Adrian.
Doesn't Swish-e pose an incompatibility for licensing? Everything Django
has been BSD up to this point and I would hate to see anything alter
this. Isn't swish-e gpl?
Regards,
David
Jacob Kaplan-Moss wrote:
On Dec 29, 2005, at 9:31 AM, Adrian Holovaty wrote:
At
Addendum:
I see one reccommendation described at:
http://code.djangoproject.com/wiki/CookBookManipulatorWithPostpopulatedFields
but I'm trying to do the inverse - allow the update of only, say, one
field and keep the rest the same whereas this example is preserving a
few and updating the
>I've always though that this particular -- and common -- use case
>should be delegated to the DB level using one of the many excellent
>replication/distribution tools for your database. For example, you
>could easily do read distribution with pg_pool or sqlrelay, and it
>would be transparent to
On 29 Dec 2005, at 20:29, Jacob Kaplan-Moss wrote:
I've always though that this particular -- and common -- use case
should be delegated to the DB level using one of the many excellent
replication/distribution tools for your database. For example, you
could easily do read distribution
On 12/27/05, James Bennett <[EMAIL PROTECTED]> wrote:
> When writing a view which will send email in response to input (say, a
> contact form), does a developer need to perform the sort of input
> validation common in, say, PHP, in order to prevent injection of
> additional headers?
Good call!
On Dec 29, 2005, at 9:10 AM, Adrian Holovaty wrote:
... or would you be doing more of a standard setup,
in which you'd want database reads to be spread evenly across multiple
DBs? Go ahead and explain the setup, and we can get started on
designing the feature.
I've always though that this
On Dec 29, 2005, at 9:31 AM, Adrian Holovaty wrote:
At World Online, the search engine (lawrence.com/search,
ljworld.com/search) uses swish-e (http://swish-e.org/) to index files.
[snip]
Hope that helps! It would be pretty cool to open-source this mini
search framework and pop it in
On Dec 27, 2005, at 2:17 PM, Dody Suria Wijaya wrote:
One more thing that I have not seen is overrideable "prepare new
row" method. triggered to provide customized field value, just
after model instance creation. ie:
This is addressed under "Added a more powerful way of overriding
model
Hello all!
I have been testing Django for a while and I'm trying to create my
first application. This application requieres a self relation model as
the one we have at
http://www.djangoproject.com/documentation/models/m2o_recursive/ .
It would be nice to have some kind of tree struture to edit
Michael Hipp napisał(a):
> I agree. The official tutorial starts off well, but about 1/3 way thru
> the first page is ceases being a tutorial and seems to scatter in all
> directions never to return.
>
> Alas, I'm thinking of writing one. If I ever figure it out, that is.
> Django looks great -
On 12/29/05, patrick k <[EMAIL PROTECTED]> wrote:
> while working with django for a couple of weeks now, i´m very impressed by
> the performance. the sites of my app are building up incredible fast (e.g.
> compared with rails), although i´m on a shared 8$/month environment.
Thanks, Patrick!
while working with django for a couple of weeks now, i´m very impressed by
the performance. the sites of my app are building up incredible fast (e.g.
compared with rails), although i´m on a shared 8$/month environment.
keep up the fine work.
patrick.
On 12/27/05, sarahwithanx <[EMAIL PROTECTED]> wrote:
> Why does the get__count() option only show on one side of the
> ManyToMany relationship?
>
> I am using 'limit_choices_to', which also appears to be one-sided, and
> I cannot easily get an object count from the table including the
>
On 12/28/05, Yuri T. <[EMAIL PROTECTED]> wrote:
> Another possibility to consider is adding error messages for import
> cases. Django seems to do a lot of magic with importing, which makes
> hard for the user to figure out where exactly it expects to actually
> find the modules. Perhaps it
On 12/29/05, wang bin <[EMAIL PROTECTED]> wrote:
> I have seen a very nice select field in
> http://c82.net/samples/checklist-samples.html, I am curious could i
> write a custom field to achieve that and using it in other projects?
For something like that,
On 12/29/05, Scott johnson <[EMAIL PROTECTED]> wrote:
> Now I haven't hacked Django much myself yet (I've been working on the back
> end tools, db loader and overall schema). What support does Django have for
> multiple db stuff?
Hey Scott,
Welcome!
Django doesn't support multiple DBs out of
Alice wrote:
I'm trying to access the username of a journal post in a generic
object_detail/list view like this:
{{ object.poster.username }}
however I'm not getting anything whatsoever ... my model is
class Journal(meta.Model):
poster = meta.ForeignKey(User, editable=False)
works like a charm, thanks.
Alice
Hello, *Long time lurker; first time poster*. My partner and I are standarizing on Django / Python for the front end of www.ookles.com, our new startup. We're both php folk and I've convinced him that Django is better than ruby (based, honestly, on my respect for Simon and Adrian rather than a
On 2005-12-27, at 14:34 CET, PythonistL wrote:
MEDIA_ROOT = "/Media/" # because of alias in httpd.conf
MEDIA_URL = "http://localhost:8080/Media/;
Is the settings.py correct?
No, MEDIA_ROOT is filesystem path and MEDIA_URL is URL path:
MEDIA_ROOT='C:/Django/TEMPLATES/Static/'
MEDIA_URL =
Thanks!That's it!
I'm misssing the '/' at the end of the action.
On December 29, 7:18 pm "martin xus" <[EMAIL PROTECTED]> wrote:
>
> here are the codes:
> from django.core import meta
>
> class Category(meta.Model):
> name = meta.CharField(maxlength=20)
> parent = meta.ForeignKey('self', null=True, related_name='child')
>
>
>
26 matches
Mail list logo
