#django

ok

The only other option is a delimiter as you mentioned, maybe making a custom field type to do it.

and if you use prefetch_related(), it will not be a join at all, you'll just get your files in a second query

But FK is the optimal approach

_but_ for the purposes of benchmarking, consider an ArrayField

That exists?

in PostgreSQL, yes

Ah

yeah found this solution as well but its a bit hacky IMO as it already relies on postgres then

can someone recommend a mongodb backend on django? i'm not really happy with the SQL stuff :/ i only found mongodb-engine which seems dead (2 years w/o commit) and django-norel which has mongodb support is also heavily outdated (is on django 1.5)

or another framework like django without the SQL limitations?

XHFHX: Django's ORM is tied to SQL and tables heavily

I would first try PostgreSQL as a NoSQL backend - with ArrayField and CompositeField, you can get some interesting results

i really like the whole infrastructure of django but that those models have to fit a SQL database is not my taste

Koterpillar: the porject has probably has to run on microsoft sql at some point... :/

...then how is Mongo going to help?

good point^^ well, as its mongo i could say it cant run on as SQL

i could store the jsons properly

dont have to write for every little bit a model

Ah, then it's a management problem then :)

-then

yes ;)

if sql, then MS SQL

To put it the other way: PostgreSQL is specifically banned

very likely yes

ibind :: (a -> m j k b) -> m i j a -> m i k b

sorry, ignore

How do I clear migrations from showing up in ./manage.py show migrations? They still continue to show and I can't seem to migrate. I'm looking for a fresh start of my database for a project I just started.

I've deleted the migrations directories and dropped/recreated database already and it still shows.

you will still see migrations from Django's apps, but you don't need to clear those, as they work.

"can't seem to" -?

why use formset_factory over a list of forms?

toothe: it is a glorified list of forms

toothe: why use a form over a list of fields?

someone was writing a library to unify forms, fields and formsets, but it looks like it stalled

personally, I'd go with a superform wrapper if I need a formset

Koterpillar: touche

Ironically, I'm now trying to write a form-like that autosaves from JS to DRF

What is the right way to create an object from a DB row which contains (among other fields) the classname?

I want to use this classname to create the model object from the DB

contenttypes

porton: maybe you should have a look into the contenttype framework

porton: and think what would happen if someone stores 'subprocess.Popen' in that field ;)

Koterpillar: we have full control over this field

porton: defence in depth

porton: do you have an ID field next to it?

Koterpillar: yes

then you've reinvented contenttypes

Koterpillar, I figured it out, didn't notice you responded to me. I had to run make migrations on my app before migrating.

dcrouch: pretty sure it tells you to

Upon trying to createsuperuser from my custom user I get this. https://dpaste.de/KRQb I know I should override REQUIRED_FIELDS, I added first name as one... Still failing.

why are you using get_field_by_name?

and what for? You have your model, just declare the field on it with unique=True

Koterpillar, Had that, removed required_fields and it failed, here's what I have. https://dpaste.de/XtYs

that's not what you have in the error

Koterpillar, a guide I followed had me add something and I modified since my last paste. :(

Koterpillar, current https://dpaste.de/ANHa

you have to override create_superuser

to do that, override the manager on your User

look up which base class to use in the Django docs I'm assuming you already have opened

hi.

i've been using sqlite3 as my db for django and want to shift to postgres

is it relatively seamless?

depends