Hi José,
On Tuesday 03 November 2015 12:58:54 José Tomás Tocino wrote:
> El lunes, 2 de noviembre de 2015, 13:22:17 (UTC+1), Shai Berger escribió:
> > https://code.djangoproject.com/ticket/6148
>
> That ticket seems somewhat related, but the feature we're dealing with here
> is, in my opinion, muc
Hi Shai
First of all, I'd like to point out that I don't have experience working
with different schemas, so bear with me if I don't fully comprehend the
ticket you've referenced.
1) Some progress has been made on the "support schemas" ticket lately, and I
> believe that completing that ticket may
Since we're on the topic, it'd be great if `inspectdb` also accepted a
`--tables` option, to only move certain tables in the database. For example:
./manage.py inspectdb --tables=form_*,user_*
...to import any tables starting with 'form_' or 'user_'. Allow with the
`--database` option, this wou
Just to make sure we're talking about the same thing:
Are you doing something like "inspectdb other.a other.b" or "inspectdb a b"?
I was writing assuming the first.
Beyond that -- the attitude we've always taken with inspectdb is to just make
it get all the tables, and let the user delete model
>
> Are you doing something like "inspectdb other.a other.b" or "inspectdb a
> b"?
>
The latter. Given a single database (and the default schema), my patch
allows to just inspect tables "a" and "b".
> Beyond that -- the attitude we've always taken with inspectdb is to just
> make
> it get all th
On Wednesday 04 November 2015 16:46:35 José Tomás Tocino García wrote:
> > Are you doing something like "inspectdb other.a other.b" or "inspectdb a
> > b"?
>
> The latter. Given a single database (and the default schema), my patch
> allows to just inspect tables "a" and "b".
>
Now I get it. Ther
Details are available on the Django project weblog:
https://www.djangoproject.com/weblog/2015/nov/04/bugfix-release-issued/
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group an
>
> In that case, are you sure what you're offering is a solution and not just
> a
> workaround? Shouldn't we make it so that inspectdb always gets all the
> tables
> in the schema?
>
Well, as far as I'm concerned, I'd rather be able to choose what tables I
want to work with. In fact, I'm not sure
I have initially created the ticket
https://code.djangoproject.com/ticket/25618 which addressed the bug that
would occur if south migrations somehow ended up being still present in the
migrations module.
According to a report in:
https://code.djangoproject.com/ticket/25618#comment:7, this seem
On Tuesday, November 3, 2015 at 5:17:32 PM UTC+1, Asif Saifuddin wrote:
>
> I would like to create an experiemental repo on my github for
> experiementing the sqla support to django orm, hence some useful resource
> indicator would be great. sqla have core engine and orm on top of it, so
> the
Hei,
I tried several frameworks, but django is my favorite for many reason. I
have some familarities with django internal code and mechanism. sqlalchemy
integration with django is a challenging task as dj admin and forms and
some other thinks need to be figure out.
Cheers
Asif
On Thu, Nov 5, 20
Hi Asif,
On Wed, Nov 4, 2015 at 12:17 AM, Asif Saifuddin wrote:
> I would like to create an experiemental repo on my github for
> experiementing the sqla support to django orm, hence some useful resource
> indicator would be great. sqla have core engine and orm on top of it, so
> the idea way to
that's an awsome link :)
thanks russ.
On Thu, Nov 5, 2015 at 12:03 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> Hi Asif,
>
> On Wed, Nov 4, 2015 at 12:17 AM, Asif Saifuddin wrote:
>
>> I would like to create an experiemental repo on my github for
>> experiementing the sqla supp
It's actually quite common pattern in Oracle to create tables using
special admin user and then create separate users that just do have
spesific priviledges per table.
Specially old Oracle docs promoted such a pattern.
In my opinion current behavior is just fine. Also I think inspectdb
doesn'
>
> In my opinion current behavior is just fine.
How is it "just fine" if there are usecases (the one I've described, for
instance) where the current behavior evidently doesn't cut it?
>
>
> On 04.11.2015 18:26, Shai Berger wrote:
>
>> On Wednesday 04 November 2015 16:46:35 José Tomás Tocino Ga
15 matches
Mail list logo
