put into an existing infrastructure and there isn't
the freedom at this point to change it. Even with this being the case,
I think this could quite easily bite others, and it's pretty trivial
to fix.
--
Regards,
Ben Ford
ben.for...@gmail.com
+447540722690
Joan Crawford - "I, Joan Crawfo
e job just keeping the damn thing running.
>
> I've more or less given up and am working on pony-build instead. Watch
> this space.
>
> Jacob
>
> >
>
--
Regards,
Ben Ford
ben.for...@gmail.com
+447540722690
Charles de Gaulle - "The better I get to know men,
Merging - no. Cross linking, yes, in conjunction with relevant
> additional content:
>
> - The HowTo should have a step-by-step walkthrough of the process of
> building a specific custom field, with a link to the topic guide and
> reference.
> - The topic guide should hav
to make sure that the elaborate charade we play (conning windmill
> to play with us) is reliable for 3rd party applications as well.
>
> The branch isn't really ready for testing yet, but it has been known to
> work. And Eric has kindly thrown up a coverage report!
>
> http://med
; > http://code.djangoproject.com/ticket/6845 is.
> >
> > Is the github code useable for production? Is there anything I can do
> > to help with it? Is there a recommended workaround for model
> > validation in the meantime?
> >
> > Thanks,
> >
> >
an upstream app already had tests
and was using fixture, then you could use those fixtures to provide the data
where your models are referring to the existing ones.
Thanks for your time on this Malcolm, it's certainly given me an idea of
what to look at next and where I might be reinventing the
3. At the moment you can only specify a relationship from the direction
that the field is defined. i.e as we have Book -> fk -> Author you can't
write a dataset the does:
class app__Author(DataSet):
class auth1:
...
books = [app__Book.book1, ...]
I made it work this way to simplif
eally in favor of using or not using them, but I'd just like
> to know if they're in the plan, in case I should add some notes in my
> ... documentation.
>
> -Gul
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~
d @register.tag(token_stream=True) work instead, or am I missing
> > something?
>
> Yes, that would work.
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You received this message because you are subscribe
django
in the Oxford area
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
be good!
Ben
2008/7/22 Tom Dyson <[EMAIL PROTECTED]>:
> Hi Ben
>
> Some of us (at Torchbox) would be interested, depending on dates. Are you
> planning to coincide it with one of the main Django sprints?
>
> Cheers
>
> Tom
>
>
> On 22 Jul 2008, at 09:51, Ben Ford
obviously help!
Cheers,
Ben
2008/7/22 Ben Ford <[EMAIL PROTECTED]>:
> Hi all,
>
> Appologies for being a couple of weeks late with this... I'm currently
> working for in a team developing a django site and we'd like to offer our
> facilities (office space, wireless, tea making et
> > to a specific server based on some arbitrary logic).
> >
> > I may have misunderstood the proposal, but I think it's vital that the
> > above two use cases are considered. Even if they can't be solved
> > outright, providing tools that custom solutions to these cases
Nunez Gomez <[EMAIL PROTECTED]>:
>
> <http://hg.dpaste.com/django/>
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goog
uot;Django should use
> > Git!" thread; if you do I'll just ignore you. We're not switching from
> > SVN any time in the foreseeable future.
> >
> > OK, so the details:
> >
> > Repository: git://djangoproject.com/django
> > Gitweb:http://code.djangopro
Thanks Graham,
I though that might be the case, I won't bother to raise a ticket then.
Ben
2008/6/17 Graham Dumpleton <[EMAIL PROTECTED]>:
>
>
>
> On Jun 17, 1:28 am, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > I've come across
;
> i found it vary useful in production in when debugging error that can
> not be recreated in the django development server.
>
> Thanks
>
> -Mark Zitnik
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~-
uraged? (django's documentation would suggest the use of request.path)
Cheers,
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
t
> runtime, from which db_table could be determined, i.e.
> Product.objects.all(ctx) where ctx.db_table is the name of the product
> table I wish to use
>
> That is a very quick and dirty example, however I hope I have still
> made sense and might be able to get some
tickets perhaps the wiki might be a good
place to discuss the API? Anyone can clone from the hg repo, give me a shout
if you would like push access and I'll sort it out.
Cheers,
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You
would be to return the connection defined in settings.DATABASE_*. The code
to build the declarative DatabaseWrapper is already there, and there a
method to build one of these from what's in settings too. This should make
it easy to get hold of connection in all of
't, I see if I can at least make enough time to write up the API
> > I came up with at PyCon.
>
> Please do, that would be great.
>
> --
> Nicola Larosa - http://www.teknico.net/
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~
queryset-refactor merge will cause all sorts
> of headaches for this branch.
>
> If you are willing to take on the challenge of handling any bugs that
> you find, and managing the merge process for any new features from
> trunk that you want, then you will be able to use multi-db. H
well, in case
> they're not reading django-developers at the moment. I don't really
> care who takes it on, just as long as people aren't waiting on me for
> it anymore.
>
> -Gul
>
> [1] http://code.djangoproject.com/ticket/6390
>
> >
>
--
Regards,
Ben Ford
[EM
s dead, and there are patches being
> attached to #4747? I'd be willing to pitch in some time to get the
> multi-db code up to snuff, if there is a clear road ahead for what
> needs to be done. If there isn't I can live with that too :-)
>
> /
Sorry for the forward, forgot to add the dev group when I sent the mail!
-- Forwarded message --
From: Ben Ford <[EMAIL PROTECTED]>
Date: 11 Oct 2007 10:14
Subject: Re: Multiple DB-Support at django
To: BIERMANS Koen <[EMAIL PROTECTED]>
Cc: "Adam, Mario A
s for your thoughts. Hopefully I can introspect all the
> relationships and have back references working automatically before I
> go home tonight.
>
> Paul
>
> On 10/5/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Hi Paul,
> >
> > I don't think it would entail t
ORM fields with the
> > > Model.field syntax (as they would be replaced by SA's).
> >
> > Could you use the post_init signal to attach a LazySAModel object as
> > an SA (or something) property of all newly created Django models?
> >
> >
> > >
&
If there's enough interest I'll move forward
> with filling out the corners.
>
> Thanks,
> Paul Davis
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+6281317958862
--~--~-~--~~~---~--~~
You received this message because you are subs
Hi Ian,
There was some funky code in the branch I'm using and query.py wasn't
getting the correct subclass of _QuerySet.
Ben
On 04/10/2007, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
>
> On 10/3/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Hi Ian,
> > OracleQuerySets
/base.py to return ''. it seems this is going to be addressed in the
queryset refactor coming shortly.
Ben
On 04/10/2007, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
>
> On 10/3/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Hi guys,
> > Thanks for the reply. So if my only
t; queryset-refactor branch, please don't hesitate to ask.
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+6281317958862
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&qu
easier for people to
share/use/develop further, which can only be a good thing!!
Thanks
Ben
-- Forwarded message --
From: BIERMANS Koen <[EMAIL PROTECTED]>
Date: 14 Sep 2007 21:52
Subject: RE: Ticket 4747
To: Ben Ford <[EMAIL PROTECTED]>
Hi Ben,
In annexe a diff of
Thanks for the input and the info. I'll have a look at those issues and
hopefully get them sorted before the sprint.
Ben
On 12/09/2007, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 9/12/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Thanks for the responses
gest some suitable
> > candidates.
>
> I've read the announce. Well - unfortunatetely it IS a friday, what's
> a normal working day for me. But maybe there's time at the evening.
> I'll see...
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~
and leave it otherwise untouched. Which I think would
> be pretty sweet.
>
> I've posted this to developers as I think it requires some in depth
> knowledge of how Django does its job. Apologies if it's a bit off
> topic.
>
> Hope this inspires someone.
>
> Regards,
>
ely doable- it's form right now is
> just a left over from how I went about pinning down what ops were
> 'standard' for backends. Crap like that will be removed next time I
> do a full walk of the changes (this round is basically a "this is the
> api I'm proposing, a
Yes, word for word damnit!
Wish I'd seen that before I started messing... Still it taught me a bit more
about postgres I guess so it's all good! :-)
Cheers,
Ben
On 12/07/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
>
> Ben Ford wrote:
> > Peter,
> > I ran into this
ngo.trunk/.
>
> Since you're on svn, you might also try svk.
>
> -Forest
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGlOZHRO4fQQdv5AwRAspiAJ9D3/FKYTeCw42vQok6M5u6EXnpEQCeMKbL
> 6n8oBKPFqBWhjKQxYQt09cI=
> =pqb0
> -END PG
get_relations(cursor, table_name)
>
> File
> "/usr/lib/python2.5/site-packages/django/db/backends/postgresql_psycopg2/introspection.py",
> line 35, in get_relations
> relations[int(row[0][1:-1]) - 1] = (int(row[1][1:-1]) - 1, row[2])
> TypeError: i
ews on updating the svn repo for this branch ?
>
> k
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&
apply it to trunk and
have fun with it... There are some problems with the tests on my machine,
basically i can't get them to run properly, so if anyone could look into
that it would be great, I'm guessing that the tests will be somewhat
incomplete!
Thanks
Ben
--
Regards,
Ben Ford
[EMAIL PRO
the django_session table in my test database (running postgres) around about
the place where the output says "Request a page that modifies the session
... ok" i'm not sure what's going on and I don't think I know enough about
it to find out in a reasonable space of time.
Thanks
Ben
--
Regards,
Ben F
tabase
>name with the local model.
Essentially, that's what this bit is doing:
rel.to._default_manager.connection
In muti-db the model's default manager keeps a reference to the db.
I'll see if i can have a play with the tests and nail it down a bit
better!
Ben
--
Regards,
Ben Ford
[
SELECT * from thisdbmodel WHERE pk_column in
(list_of_fk_values); #run on the main db
What do you think?
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&
On 08/06/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 6/8/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Hi Russ,
> > Thanks for the reply. What's the prescribed way to track multiple
> patches in
> > one working copy? I haven't had much experien
k it might
be a fairly elegant way to solve some problems, and would be interested in
getting some feedback...
Thanks,
Ben
On 08/06/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 6/8/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> > Russ,
> >
> > Can I
feature, open one, and keep the
> patch up to date.
>
> Once you demonstrate that you're (1) capable of doing the work, and
> (2) are in this for the long haul, we can get you an SVN login for the
> branch.
>
> Yours,
> Russ Magee %-)
>
> >
>
--
Regards,
Ben
this checked into django so other
people can work on it, if there's still any interest...
Thanks in advance,
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
()]
> else:
> pass #not queryset
>
> def set(self, key, value, timeout=0):
> self._fill_qs_cache(value)
>
> self._cache.set(key, value, timeout or self.default_timeout)
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+6
rate with legacy systems; the
number of responses to the 'database connection' thread I mentioned above
would appear to bear this out.
I'd be very interested to hear peoples' opinions on this subject.
Thanks for reading,
Ben
--
Regards,
Ben Ford
[EMAIL
search around on the subversion site, but I thought
> > > someone might have a link to a good site with a list of common how-to
> > > bullets that might be quickeror that someone might just be kind
> > > enough to paste the command they use into a reply.
> >
&g
n before the
> merge to trunk, so backwards incompatible changes would hit with one
> merge.
>
> The ticket: http://code.djangoproject.com/ticket/4027
>
> So, what do you think about this? I'll be happy to hear your ideas.
>
> regards,
> Marek
>
> P.S.: I'll try to
recommended
> on the "Contributing to Django" page. There are some minor
> architectural changes in there, although we've made every effort to
> minimize the overall deltas.
>
> Please review the patch if you're able to and let us know what you
> think.
>
>
> >
&
und, but there are a number of reasonable tutorials and you
> can't break *too* much :)
>
> http://svk.bestpractical.com/view/HomePage
>
> Rob :)
>
> --
> One Track Mind Ltd.
> PO Box 1604, Shortland St, Auckland, New Zealand
> Phone +64-9-966 0433 Mobile +64-2
the django-gis directory (where I checked out the
gis branch)
Once again sorry for the OT-ness of my email.
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&qu
in a
bit more thoroughly.
Any information gratefully received :)
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
57 matches
Mail list logo
