#django

hi

can someone guide me here

guys?

welcome

i want to start using a framework for web dev. now i have a problem I am looking at laravel and django I want to choose one and dont look back

i will be using auth ajax messaging system and image manipulation

should i go to laravel or django?

django

if you can use django, is the best

can you guys give me more details pls

english or spanish is ok

The best way to choose is to try them both.

i dont have time for that

i need the more featureful and most fast to develop

Django's tutorial can be done in an hour, I assume Laravel has something similar.

bonjour :)

could someone help me setup django-allauth with github?

what do I give in "Key" field?

hello guys o/

good morning

i've just added a new class in models.py, but i'm not able to make a migrate.

Your models have changes that are not yet reflected in a migration, and so won't be applied.

Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

that's what it says.

and this is when i try running that command:

paradisee@Paradisee-Main:~/Documents/Django/ReatinaShop$ python3 manage.py makemigrations

You are trying to add a non-nullable field 'brand' to product without a default; we can't do that (the database needs something to populate existing rows).

do i have to manually edit each row with the missing column/field?

or is there a way to avoid that, by simply adding a Null value, or something like that.

In the field `brand` that you've added in models.py. Either make it null=True, or add a default=<some_default_value>. Whatever logic suits your application

brand = models.ForeignKey(Brand)

Paradisee: And then it says "Please select a fix"

this is the field.

ya mattmcc, but i need to understand what to place inside that field.

How would you determine the brand that all existing rows should have?

what does that mean

The field isn't nullable, so it has to have a value for each currently existing row.

by adding null=True, should work, if i let do that to django itself.

is there a way to make a specific field not required?

That's what null=True means. Although you'll also want blank=True for model validation purposes.

This field is required.

with null=True.

As I was saying, you'll also want blank=True for model validation purposes.

FunkyBob: How do I make a ModelDataMapper include a field on serialization but ignore it when a user uses the mapper to create a new object. I.e. Include the primary key but don't allow the user to set it during creation.

I can't find any docs on that

MarkusH: define a @field for it, without a write option?

without a setter, that is

by default setter does nothing

FunkyBob: alright, and where do I e.g. set the creator for an object based on request.user?

mmm?

not sure I understand

the complement to "form.instance.owner = self.request.user" in "form_valid()" on a CreateView

well, since the datamapper doesn't save...

you cal _apply or _patch then do what you like

ah, ok

in the CBV it'd be in post_valid or put_valit or...

damn, am still impressed by this -- https://www.youtube.com/watch?v=3MteSlpxCpo

ahh, damn, now I understand the logic behind the mappers

Thanks

:)

they're just "properties by proxy"

manage.py migrate isn't applying my modification in my models

I've added 3 fields but they won't get created in db