samba.git/python/samba/netcmd/domain/models/model.py, branch talloc-2.4.2

netcmd: models: add readonly attribute on fields to exclude it from save

2023-11-22T23:35:33+00:00

There was trouble when saving fields like is system object, these need to be excluded on save.

Signed-off-by: Rob van der Linde 
Reviewed-by: Douglas Bagnall 
Reviewed-by: Andrew Bartlett

netcmd: models: get_base_dn returns default rather than be abstract

2023-11-22T23:35:33+00:00

Signed-off-by: Rob van der Linde 
Reviewed-by: Douglas Bagnall 
Reviewed-by: Andrew Bartlett

netcmd: models: fix incorrect return type should not be User

2023-11-15T04:05:34+00:00

Signed-off-by: Rob van der Linde 
Reviewed-by: Douglas Bagnall 
Reviewed-by: Andrew Bartlett

netcmd: models: Model.query method makes use of Query class

2023-11-15T04:05:34+00:00

Signed-off-by: Rob van der Linde 
Reviewed-by: Douglas Bagnall 
Reviewed-by: Andrew Bartlett

netcmd: models: add FieldError subclass which stores the field

2023-09-29T02:18:34+00:00

This is so that errors on the CLI show the field name

Signed-off-by: Rob van der Linde 
Reviewed-by: Douglas Bagnall 
Reviewed-by: Andrew Bartlett

netcmd: models: field to_db_value needs ldb param

2023-09-29T02:18:34+00:00

Required by SDDL field type added in next commit

Signed-off-by: Rob van der Linde 
Reviewed-by: Douglas Bagnall 
Reviewed-by: Andrew Bartlett

netcmd: domain: add model exceptions and error handling

2023-06-25T23:29:32+00:00

* Only handle what we know, otherwise raise the existing LdbError
* Cutom messages added in the model layer so we don't have to do it in
  the commands themselves

Signed-off-by: Rob van der Linde 
Reviewed-by: Andrew Bartlett 
Reviewed-by: Joseph Sutton

netcmd: domain: model stores ldb message for save

2023-06-25T23:29:32+00:00

The message is stored in self._apply which also gets called by
self.refresh()

This is the better thing to do than fetching in save.

Signed-off-by: Rob van der Linde 
Reviewed-by: Andrew Bartlett 
Reviewed-by: Joseph Sutton

netcmd: add domain models and basic model layer

2023-06-25T23:29:32+00:00

The ORM is somewhat inspired by Django, but it has some key
differences that make it work better with the Ldb database.

A field can be a singular value or a list, so a BooleanField can
either be True, or [True, False, True], or None.

The only thing that many=True does is say that the field "prefers" to
be a list, but really any field can be a list. For example when
creating a new object, it initialises the field as an empty list
rather than None if many=True.

When saving an object, if it is an update operation, only write the
fields that have actually changed.

When updating an object, any fields that are unset (set to None, or an
empty list) will be treated as a REMOVE operation.

Note that silo members should not be saved this way, writing the whole
list can lead to data loss if multiple admins are saving the silo at
the same time. Silo members will need to be handled differently, just
removing one member but not writing the whole list.

Unlike Django, there is no .objects class, instead there are a bunch
of static methods for querying:

  * Model.get
  * Model.query
  * Model.create
  * Model.get_or_create

Signed-off-by: Rob van der Linde 
Reviewed-by: Andrew Bartlett 
Reviewed-by: Joseph Sutton