One question I'd ask would be why you wouldn't just save the files either
on disk or even in the database (using the BLOB datatype) if it absolutely
had to be in the database... then if you needed to manipulate/display/read
them at a later date you would just load the files in question.
If yo
it means that I can't do it on MySQL database! should I change the DB type
and if so which one should I prefer!
Postgres or NoSQL?
On Tuesday, July 3, 2018 at 3:20:40 AM UTC+5:30, Melvyn Sopacua wrote:
>
> On maandag 2 juli 2018 21:33:35 CEST hardik dadhich wrote:
>
>
>
> > Can anyone tell me
or you can move to postgres and take advantage of the jsonfield integration
with django.
On Monday, July 2, 2018 at 3:48:46 PM UTC-4, hardik dadhich wrote:
>
> Hello,
> Can anyone tell me how can I make dynamic Django model fields? I mean to
> say that I want to save excel file data in Django mo
On maandag 2 juli 2018 21:33:35 CEST hardik dadhich wrote:
> Can anyone tell me how can I make dynamic Django model fields? I mean to
> say that I want to save excel file data in Django model using MySQL. and
> excel column can vary. The user can upload 100 column table or he can be
> upload 1000
Hello,
Can anyone tell me how can I make dynamic Django model fields? I mean to
say that I want to save excel file data in Django model using MySQL. and
excel column can vary. The user can upload 100 column table or he can be
upload 1000 column table in the database. so it is possible to add
dy
Olivier Guilyardi wrote:
> I'm still a python newbie, but it seems to me that there could be a way to
> modify the model definition before Django knows about it:
Okay, I found the Field.contribute_to_class() method which seems to work just
fine. I'm calling it right after my model class declarati
Tim Chase wrote:
>> Actually the labs where just an example: one laboratory will
>> have one installation of the application, and the dynamic
>> fields will only apply within the scope of this installation.
>> There's no such thing as consistency accross labs.
>
> It still sounds like the above s
> Actually the labs where just an example: one laboratory will
> have one installation of the application, and the dynamic
> fields will only apply within the scope of this installation.
> There's no such thing as consistency accross labs.
It still sounds like the above scheme would do the trick.
On Apr 11, 1:36 pm, Olivier Guilyardi <[EMAIL PROTECTED]> wrote:
> However, watching the MySQL verbose log, I realized that retrieving properties
> as well as their definitions (and enumeration values) to properly display an
> detail view or edition form execute a _lot_ of SQL queries, when this c
Tim Chase wrote:
>> I'm in the process of turning telemeta [1] into a django
>> application, and need dynamic model fields: we want to allow
>> site administrators to easily add/remove "fields" to our main
>> data structure, the MediaItem, which represen
> I'm in the process of turning telemeta [1] into a django
> application, and need dynamic model fields: we want to allow
> site administrators to easily add/remove "fields" to our main
> data structure, the MediaItem, which represents an audio/video
> resource.
>
Hi,
I'm in the process of turning telemeta [1] into a django application, and need
dynamic model fields: we want to allow site administrators to easily add/remove
"fields" to our main data structure, the MediaItem, which represents an
audio/video resource.
Example: for a
12 matches
Mail list logo
