This is exactly the ticket my issue is about, des. I'll follow the Konversation there.
Thanks Stephen.
Greets,
Christian
Am 17.09.2019 18:19 schrieb "Stephen J. Butler" :Maybe I'm misunderstanding, but tablespace has to do with physical storage of the schema, not how tables are named. What you rea
You're right Oracle has quite few levels of storage definitions tablespaces
just being one.
ti 17. syysk. 2019 klo 19.20 Stephen J. Butler
kirjoitti:
> Maybe I'm misunderstanding, but tablespace has to do with physical storage
> of the schema, not how tables are named. What you really want is a
Maybe I'm misunderstanding, but tablespace has to do with physical storage
of the schema, not how tables are named. What you really want is a
db_schema_name or something. I think this long, old ticket is related
https://code.djangoproject.com/ticket/6148
On Tue, Sep 17, 2019 at 10:27 AM Christian
...
Also in Oracle you can create synonyms (private are enough) to get around
prefix.
And IIRC there is a way to set default schema for user but I that would
require executing piece of SQL after connection is made.
ti 17. syysk. 2019 klo 18.27 Christian González <
christian.gonza...@nerdocs.at>
Hi.
Unfortunately there currently isn't such a feature.
This would be interesting feature to have. Surely there are quite few edge
cases where prefixing would fail.
ti 17. syysk. 2019 klo 18.27 Christian González <
christian.gonza...@nerdocs.at> kirjoitti:
> Hi,
>
> I don't know if this is a mi
Hi,
I don't know if this is a missing feature. But after reading the code of
django.db.backends.oracle.* I think that there is a feature missing - at
least in the Oracle driver - you can't add a generic table prefix.
I have a production Oracle database where a proprietary software does
read/write
