The single piece of Django that I'm most hungry for right now is the
bit that pushes translated strings up into your javascript.
If it's feasible to use just that bit, and keep my own connection
paradigm, it could be a short-term solution.
Thanks again all for your time and energy on this thread
I am surely guilty of muddling the conversation from the specific case
of multi-DB to the more general and more perilous case of dynamic
connections. In fact I'm using the multi-db branch now for a non-
critical app and it works just dandy. Also I know of someone who is
working on updating that
On May 11, 6:32 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> user: Hi I'd like to be able to connect to multiple databases and/or
> specify connections dynamically for my Django app.
>
That wasn't what the original poster said:
"I'm managing a programming team that's developing a web
I think we have reached the dead horse phase of this discussion.
Since it has become so lengthy and confusing for some (at least for me
it has), I wanted to summarize what was accomplished. Thank you all
for your responses. I feel like I have a much better sense of
Django's current intended targ
Hey Waylan,
"What you seem to be missing is that the core devs are not questioning
that."
Ok, I think what's happening here is that one or more of us needs to
improve our communication skills - present company potentially
included. If you got that impression than I did not make my thoughts
clea
> well. Sure, someone mentioned the possability of some money for
> development, but that doesn't cover the long term maintianence, which is
> what the core devs are looking for.
If someone is offering to pay for development of a feature that will
enable them to use the framework for their softwa
On Thu, 2007-05-10 at 22:58 +, [EMAIL PROTECTED] wrote:
>
> I think what you're overlooking is that in some cases the issue of
> whether its the "best solution" is irrelevant. If the database is
> already in production or the policies are already set or controlled by
> an external entity, th
"While I'm not saying that multiple DB-level users and DB-level access
controls are the wrong solution, I would ask up-front what specific
real-world problem is being solved by this, and whether it really is
the best solution."
I think what you're overlooking is that in some cases the issue of
Re:
"While I'm not saying that multiple DB-level users and DB-level access
controls are the wrong solution, I would ask up-front what specific
real-world problem is being solved by this, and whether it really is
the best solution."
At the company I'm currently working for, we have a 'sister' comp
> Furthermore, in the general case, business logic is too complex to be
> implemented simply in the database layer - significant business logic
> would need stored procedures, triggers etc. which are inherently non-
> portable across RDBMS platforms.
Portability across RDBMS platforms is a pipe d
On May 10, 7:37 am, foobarmus <[EMAIL PROTECTED]> wrote:
> 1. RDBMSs like PostgreSQL, Oracle, perhaps even MySQL although it's
> still a fledgling in this regard (to name but 3), were designed to (or
> have subsequently been revamped to) handle the kind of business logic
> that large organisations
> Ultimately, this is a tradeoff. What happens when another app wants to
> use data from the same database but has less strict auth/access
> requirements? So long as you know that only one application with only
> one relatively-unchanging set of requirements will ever access the
> database, you'll
On 5/10/07, foobarmus <[EMAIL PROTECTED]> wrote:
> Unfortunately, pushing access control up the stack means I
> have to rewrite all the functionality has been carefully and
> comprehensively facilitated by my RDBMS. Also it means that access
> control logic has to be written into every app that co
James, thanks for this argument.
Perhaps I should have given some more specific info about the project.
We are at approximately version 0.2 - months or perhaps a year from
having a beta. Nothing is cast in stone.
It's important to us to implement access control at database level for
a couple of
On 5/9/07, foobarmus <[EMAIL PROTECTED]> wrote:
> It's a tightly modelled, configurable, business administration tool.
> If used in a business of significant size, I would expect and hope
> that a DBA was employed to administer the database. Many of the tables
> will contain information that is re
Hey Russ,
As always your response is sound, candid, and well thought out.
You're either nimble with your typing or you put in a little block of
time to compose that so thanks!
Just a few quick points:
1. I see now that there is a definite intention maintain a particular
profile for the framewor
Perhaps I should have given more specific info about the project.
It's not a CMS, or one of these "happy apps" that just have a database
because it's cool to have one.
It's a tightly modelled, configurable, business administration tool.
If used in a business of significant size, I would expect a
On 5/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> (quite a lot) :-)
>
Hi Brian
The primary design use case for Django development is clean room
development of a new web based application. This is what it was
originally designed for, and there is plenty of evidence around to
suggest th
foobarmus wrote:
> I'm managing a programming team that's developing a web app in python.
> I'd like to be using Django but can't at the moment because one of the
> things we are doing is driving the application user into the database
> connection, so that we can implement access control at databa
The limitation of Django's single database, single connection paradigm
is one that I have been recently grappling with. In a recent
discussion in the users group, I went so far as to call it an
"unfortunate" design decision. While I agree that the label I chose
is purely a subjective value call,
Thanks for the response, Max. It's very to the point. Much
appreciated.
> Yes. The conventional wisdom that everyone "should know" is never to
> use such web to database pass-through authentication for anything
> bigger than an intranet application behind corporate firewalls/VPNs.
>
> There are
On 5/9/07, foobarmus <[EMAIL PROTECTED]> wrote:
>
> I'm managing a programming team that's developing a web app in python.
> I'd like to be using Django but can't at the moment because one of the
> things we are doing is driving the application user into the database
> connection, so that we can i
I'm managing a programming team that's developing a web app in python.
I'd like to be using Django but can't at the moment because one of the
things we are doing is driving the application user into the database
connection, so that we can implement access control at database level.
I would like s
23 matches
Mail list logo
