Which framework did I personally spend heaps of time investigating,
book-buying and ultimately reject for my own purposes?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this g
On 19-Jun-06, at 2:04 PM, jorjun wrote:
>
> Which framework did I personally spend heaps of time investigating,
> book-buying and ultimately reject for my own purposes?
yes - we are all ears
--
regards
kg
http://lawgon.livejournal.com
http://avsap.org.in
--~--~-~--~~--
On 6/19/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> yes - we are all ears
Meh. The book-buying is a giveaway.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~-~--~~~---~--~~
You received this message because
On 19-Jun-06, at 2:38 PM, James Bennett wrote:
>
> On 6/19/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
>> yes - we are all ears
>
> Meh. The book-buying is a giveaway.
ahh - monday morning, forgive me ;-)
--
regards
kg
http://lawgon.livejournal.com
http://avsap.org.in
--~--~-
Hello.
I have submitted a patch to ticket#2197[0]. Any comments? Does anyone
else think this is useful to have in django?
[0] http://code.djangoproject.com/ticket/2197
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On 6/19/06, Matias Hermarud Fjeld <[EMAIL PROTECTED]> wrote:
> I have submitted a patch to ticket#2197[0]. Any comments? Does anyone
> else think this is useful to have in django?
It's a useful thing, but...
We've got a Summer of Code project working on a true
search-engine-like system to integr
On 6/17/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> On 6/17/06, gabor <[EMAIL PROTECTED]> wrote:
> >
> > could you post your model and the relevant part of the view code?
> >
The relevant model:
class Product(models.Model):
product_name = models.CharField(maxlength=64,
blank=False,validator_
On 19 Jun 2006, at 13:25, James Bennett wrote:
> We've got a Summer of Code project working on a true
> search-engine-like system to integrate into Django, which would
> provide searching capabilities far beyond what the database API
> offers. So this might end up being redundant.
Will the Summe
Hello
Now, I am sharing with you
another website that is excellent for IT Jobs.
Currently, this website has
6000 IT Jobs.
Please check this link and enjoy
your dream job.
www.it-jse.com
Special thing about this website
is, they are presenting direct links to jobs.
They are using only D
I posted this on django-users, but didn't get much feedback. It seems
like a pretty important problem, so I'm reposting here:
My current model looks like this:
class Article(models.Model):
title = models.CharField(maxlength=64)
slug = models.SlugField(prepopulate_from=("title",))
autho
Uros Trebec wrote:
> class Post(models.Model):
> author = models.CharField(maxlength=100)
> title = models.CharField(maxlength=100)
> content = models.TextField()
> date = models.dateField()
hi,
sorry to jump in so late into the discu
On 6/19/06, Simon Willison <[EMAIL PROTECTED]> wrote:
> Will the Summer of Code project include some kind of fall-back for
> when a proper full-text indexing system isn't available? (Something
> trivial based on LIKE queries). For small sites the .search() method
> would be very useful.
Jacob's m
I'd like to get a branch started for my summer of code project. It's
not urgent, but something in the next couple of days would be great.
http://code.djangoproject.com/wiki/GenericAuthorization
Thanks,
Joseph
--~--~-~--~~~---~--~~
You received this message becaus
Malcolm Tredinnick wrote:
> What I would like to propose is that we create a tests/regression/
> subdirectory for these slightly more mind-numbing but important tests.
> Same sub-directory structure, etc, as the the modeltests/ directory, but
> not in any way intended to be examples of good model
Don't know why Django's ORM works in this way, but I think this may be a
bug...
This is how my model looks like:
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
class Score(models.Model):
. . .
class Round(models.Model):
. . .
class Game(models.Model):
round = mode
On 6/18/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> What I would like to propose is that we create a tests/regression/
> subdirectory for these slightly more mind-numbing but important tests.
> Same sub-directory structure, etc, as the the modeltests/ directory, but
> not in any way intend
Ticket #1051 adds support for setting the schema search path on
PostgreSQL connections. I've updated the patch for the current HEAD.
It would also be interesting to look into per-application schema
search_path support, so one could have the admin app live in the
admin schema, as opposed to
I am sure you have it now. But just to make sure, the next clue is that
it sounds a bit like "soap and phone" ;0)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, s
On 19-Jun-06, at 11:28 PM, jorjun wrote:
> I am sure you have it now. But just to make sure, the next clue is
> that
> it sounds a bit like "soap and phone" ;0)
then nobody got it - because *that* is not a framework - it is an
application server, which is a totally different kettle of fis
On 6/19/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> then nobody got it - because *that* is not a framework - it is an
> application server, which is a totally different kettle of fish
Yeah. I was thinking "Booby on Whales".
Some things have a learning curve. Zope has a learning asymptote.
To better detail the "in the model" idea:
An additional field type would be added, extending CharField, called say
"HTMLSafeField". It would strip/escape/convert/reject invalid strings
both when being set and when being read. Otherwise it would behave just
like a CharField.
The key is not to t
On 19 Jun 2006, at 20:18, [EMAIL PROTECTED] wrote:
> The biggest downside is if you want valid HTML data stored for one
> output
> type and escaped for another. But this is not a scenario I've ever
> seen
> in the real world, and regardless is easily worked around with simply
> returning to
Uros Trebec wrote:
> 2.1. Basic models:
> To enable history tracking Bob has to create a sub-class for those
> models that he will like to track:
>
> class Post(models.Model):
> author = models.CharField(maxlength=100)
> title = models.CharField(maxlength=100)
>
> I'm not keen on escaping being controlled by the model - escaping
> should be a template-level decision as that's when you decide what
> format is being output (plain text email / HTML / XML / LaTeX for PDF
> conversion etc).
>
> I played around with some proof of concepts over the weekend and I
Jay Parlar wrote:
> I posted this on django-users, but didn't get much feedback. It seems
> like a pretty important problem, so I'm reposting here:
>
> My current model looks like this:
>
> class Article(models.Model):
>title = models.CharField(maxlength=64)
>slug = models.SlugField(pre
I suppose it gets brought up a lot I figure I should bring it up too so
it happens :)
I think it'd be really cool if there were a central reposatory of links
to off site tutorials and screen casts with a rating and tagging
system. That way say I created a tutorial I could go to the site, and
add
On 6/19/06, gabor <[EMAIL PROTECTED]> wrote:
>
>
> that seems to be the problem.
> it works with postgresql.
>
> if you want to verify the problem:
>
> import django.db
> print django.db.connection.queries
>
> this will print out the sql queries django is doing.
>
> in this case it does something
Database creation is silently dropping foreign key constraints where
there is more than one reference to the same primary key -- I only
caught the issue thanks to my unit tests.
Is the patch attached to #1928 a reasonable fix? It'd be great to get
this committed; it seems like a fairly seriou
On 6/19/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> It felt like a db error, because of *where* it was breaking, but I've
> not yet looked into the ORM layer, and didn't have time to start
> digging.
This feels like a reawakening of some old bugs that had to do with
matching dates in SQLite; I fo
Hi!
> There was a similar thread on this earlier where I commented about a
> slightly different way to store the changes:
> http://groups.google.com/group/django-users/browse_thread/thread/f36f4e48f9579fff/0d3d64b25f3fd506?q=time_from&rnum=1
Thanks for this one, I already found something usefull
> Sounds nice, this is a feature I'm currently looking for... but I've
> already started my own implementation.
Nice! Do you have anyting in code yet? Any bottlenecks?
> I would just share it with you.
>
> I've build a single table History with :
> - "change"; a text field which will contain a
Hi!
> Great to see that your RFC is pretty much exactly what I was thinking
> (feature and implementation-wise) when I posted
> http://roups.google.com/group/django-developers/browse_thread/thread/d90001b1d043253e/77d36caaf8cfb071
I'm glad! Thanks for the link too.
> It would be nice to record
On 6/19/06, IanSparks <[EMAIL PROTECTED]> wrote:
> Although you have a date field in your example model it might not hurt
> to add an automatic timestamp to a model that uses versioning in this
> way.
Changing the versioned model because of use of versioning is something
I would like to avoid. F
I've been developing some fun stuff with django for about a month now
and I've been thinking of taking on a big challenge, adding ZODB
support to Models.
I _love_ the django models, but there are a few things I wish to do
in which I need a full object persistence.
I'm sending this to the l
hi.
I just noticed that the last email I got from django-updates was on
june 12.
has something been turned off ?
regards
Ian
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to th
[EMAIL PROTECTED] wrote:
> that's why i suggest looking at this as a data validation issue. (not
> simply as escaping) we do lots of validation in the model already.
But it is an escaping issue.
There's nothing wrong with allowing html to be entered in (for example)
a comment field. It should
On 6/18/06, Landon Fuller <[EMAIL PROTECTED]> wrote:
> So, my plea: I like Django, and I'd like to put a lot of resources
> behind using and improving it. If new committers were pulled from the
> ranks of solid contributors, new users of Django (like me!) could be
> assured that their contribution
> > It would be nice to record "who" made the change (optionally when there
> > is a user with an id available).
>
> I was thinking of not pushing the use of such fields, because there is
> no easy way to figure out how each applications handles
> accounts/users.
and
> > I'd also like an automat
On Mon, 2006-06-19 at 12:28 -0500, Adrian Holovaty wrote:
> On 6/18/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > What I would like to propose is that we create a tests/regression/
> > subdirectory for these slightly more mind-numbing but important tests.
> > Same sub-directory structure,
On 19 Jun 2006, at 21:00, [EMAIL PROTECTED] wrote:
> anyway, i suppose i will wait for you to elaborate on your
> reasoning in
> the wiki this evening. :)
I've written up a proposal for how we can implement auto escaping
while hopefully keeping most people happy:
http://code.djangoproject
40 matches
Mail list logo
