On 27 juil, 14:37, Torsten Bronger
wrote:
(snip)
> Well, it could map them possibly ... granted that there would be no
> reason for it. Okay, then I must be more precise:
>
> If I have a model with an implicit primary key, and values of this
> key are used to identify associated files on disk, is
Hallöchen!
Steve Holden writes:
> On 7/27/2010 12:38 PM, Torsten Bronger wrote:
>> Hallöchen!
>>
>> bruno desthuilliers writes:
>>
>>> On 27 juil, 07:19, Torsten Bronger
>>> wrote:
>>>
Currently, our Django app relies on the stability of various auto
ID fields which are implicitly ge
On 27 juil, 13:38, Torsten Bronger
wrote:
> Hall chen!
>
> bruno desthuilliers writes:
> > On 27 juil, 07:19, Torsten Bronger
> > wrote:
>
> >> Currently, our Django app relies on the stability of various auto
> >> ID fields which are implicitly generated by Django/database
> >> backend.
>
> >
On 7/27/2010 12:38 PM, Torsten Bronger wrote:
> Hallöchen!
>
> bruno desthuilliers writes:
>
>> On 27 juil, 07:19, Torsten Bronger
>> wrote:
>>
>>> Currently, our Django app relies on the stability of various auto
>>> ID fields which are implicitly generated by Django/database
>>> backend.
>>
>>
Hallöchen!
bruno desthuilliers writes:
> On 27 juil, 07:19, Torsten Bronger
> wrote:
>
>> Currently, our Django app relies on the stability of various auto
>> ID fields which are implicitly generated by Django/database
>> backend.
>
> [...] From a practical POV, starting from a mint empty DB and
On 7/27/2010 8:40 AM, bruno desthuilliers wrote:
> On 27 juil, 07:19, Torsten Bronger
> wrote:
>> Hall chen!
>>
>> Currently, our Django app relies on the stability of various auto ID
>> fields which are implicitly generated by Django/database backend.
>
> auto ID are a RDBMS feature, Django is n
On 27 juil, 07:19, Torsten Bronger
wrote:
> Hall chen!
>
> Currently, our Django app relies on the stability of various auto ID
> fields which are implicitly generated by Django/database backend.
auto ID are a RDBMS feature, Django is not involved. They are usually
just sequential long ints. And
Hallöchen!
Currently, our Django app relies on the stability of various auto ID
fields which are implicitly generated by Django/database backend.
Is is better to have explicit ID fields for this or can one consider
them stable?
For example, many bitmap files on the DB server are connected with
mo
8 matches
Mail list logo