y should be changed forthwith -
however it's being 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
eeping 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, the mor
nking, 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 have a broad description of the is
later, so I expect a bit more cleanup
> next week 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
> w
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,
> >
> > David
> >
> > --
> > David Reynolds
> > da...
: facing only in the direction of
> upstream dependencies. But if you can make it worth both ways, why not?
Yep, this would be quite a nice aim, if 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
http://bitbucket.org/boothead/fixture-django/src/tip/fixture/loadable/django_loadable.py>particularly
the field_is_required function and the _check_schema method and
tell me if there's a better way to do it.
3. At the moment you can only specify a relationship from the direction
sses.
>
> I'm not really 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
companies using 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 e
ny of those would 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
that would
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, wir
multi-db solution at least take this in to
> > account (maybe just by providing an easy tool to direct an ORM request
> > to a specific server based on some arbitrary logic).
> >
> > I may have misunderstood the proposal, but I think it's vital that the
> > above tw
Ariel Mauricio Nunez Gomez <[EMAIL PROTECTED]>:
>
> <http://hg.dpaste.com/django/>
>
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
is a shot. Please don't try to turn this into a "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:
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 co
.
>
> 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
--~--~-~--~~~
elf.path?
3) Does this need a ticket or is the use of request.META['PATH_INFO']
discouraged? (django's documentation would suggest the use of request.path)
Cheers,
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+447792598685
--~--~-~--~~~---~--~~
You receive
would be needed is the ability to supply a context at
> 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 ha
to ability to create 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
--~--~-~--~~
use in a queryset (and all the other places
it's needed) and I think the correct default behaviour of the class/object
would be to return the connection defined in settings.DATABASE_*. The code
to build the declarative DatabaseWrapper is already there, and t
gt; If I don'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
--~--~--
ere still many issues to be resolved, and I
> suspect that the upcoming 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 featu
t; I'm directing this email directly to those people as 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.dj
ounds as if the branch is 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
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
ween the two model
> styles.
>
> Anyway, thanks 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 Pa
t; > > you would no longer have access to Django 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
Alchemy
> from there.
>
> Any feedback is welcome. If there's enough interest I'll move forward
> with filling out the corners.
>
> Thanks,
> Paul Davis
>
> >
>
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+6281317958862
--~--~-~--~~---
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,
> > Oracle
/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 i
e could provide on the
> 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
this
stuff should live in the limit_offset_sql function of the DatabaseOperations
class and just needs to be moved? Or is there a deeper issue causing
problems?
Thanks
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+6281317958862
--~--~-~--~~~---~--~~
You received this message
ll obviously make it 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 Be
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 respo
m
> > sure someone on the day will be able to suggest 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...
>
>
>
f into the repo, I'm perfectly happy to put myself
forward as maintainer for the branch and to make sure it stays up to date in
the future.
Thanks,
Ben
--
Regards,
Ben Ford
[EMAIL PROTECTED]
+628111880346
--~--~-~--~~~---~--~~
You received this message becaus
f this was possible then you could point the script at any database,
> browse and edit, 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. Apologi
d there is no
> complaint about 2-10 lines below where it's shoving a curried func
> into locals (half expected a knee jerk "yuck" on that one ;).
>
> As indicated further up, those two classes will need another cleanup;
> the currying/locals I'd adv
uto_now in
> the admin_log model to work (it bypassed the valuesetting in the DateField
> class.
>
>
>
> A first try in a little app of mine seems to work now. I will try to see
> if I can get some of the testsuite working.
>
>
>
> Thanks a lot for the good work! D
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
http://hg.korpios.com/django.trunk/.
>
> Since you're on svn, you might also try svk.
>
> -Forest
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGlOZHRO4fQQdv5AwRAspiAJ9D3/FKYTeCw42vQok6M5u6EXnpEQCeMKbL
> 6n8oBKPFqBWhjKQxYQt09c
ntrospection_module.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
here any news 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 deve
an interest to 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
--
Reg
ing missing in my environment
> > or the way I run the tests or what?
>
> Whoops; you've found a subtle bug -- not sure if it's a code bug or a
> documentation bug yet. Change your SITE_ID value to be something other
> than 0 and the tests will pass, at least for the latter c
ked... They are basically locking up
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 re
atabase
>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
eld = 'whatever'; #run on the other db
and:
final_query = 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 t
o make it work too!!
Ben
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 cop
consideration. I think 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,
&
r the multi-db 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 %-)
>
> >
>
as of rev 5371, it might be good to get 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 becaus
nstance(value, dict):
> [self._fill_qs_cache(part) for part in value.values()]
> else:
> pass #not queryset
>
> def set(self, key, value, timeout=0):
> self._fill_qs_cache(value)
>
> self._cache.set(key, value, timeout or
reality for me, and I would suggest it
would be for a lot of people who have to integrate 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 hea
e trunk.
> >
> > > Yes...I could go 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 pas
inst newforms-admin, maybe even 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,
>
#x27;re advertising it here as 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
some time to get
> your head around, 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 Zealan
ltiple-db-support .
#this done while I was in 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
hering you. But I want to make sure you
> don't duplicate work ;-)
>
> Ciao,
> - Matthias
>
>
> On Mar 25, 5:53 pm, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I've been playing with an Oracle database at work today and after a bit
> o
hat I didn't have time to dig 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 de
62 matches
Mail list logo
