pdm | A modern Python package manager with PEP 582 support

The base64 value you provided in your question is malformed, my recommendation is to not use Json Serialization for this Api response effort.

Try using Convert.ToBase64String

• Ensure the method returns string
• and the jQuery request accepts/expects text for dataType response.

Here is an example, which does that with some arbitrary criteria to write in red some Columns in a Physical Data Model, when their name contains a "b"... using the ObjectCompositeSymbol.SubObjects attribute.

You have to replace this.AddChild(host); with this.Content=host;. Be aware, that such a way host will be the only content.
If you want to have some additional controls in the UserControl you will have to define the ControlTemplate with these controls and e.g. ContentPresenter in it.

The replacement in re.sub() can be a function. It can convert the matched string to an integer and multiply it.

If I understand your question correctly, you want to add new technical fields (I guess Extended Attributes) when you apply a Stereotype to an object (e.g. PDM Table).

You just add Extended Attributes under the Table stereotype in the Extension:

And they will appear in the Table property sheet, in the Extended Attributes tab:

You can then get a nicer display, by defining a custom form of type Property Tab, in the extension, under the same stereotype, to present properly your extended attributes.

I am sticking to the Relational Database context, that you have tagged.

Data Modelling is an iterative process. There is a lot more definition that is needed, before the data model can be complete. Rather than answering the specifics that you request, which would be limited to one iteration; one increment, allow me to provide something more complete, several iterations progressed.

If it is useful, please discuss this data model, and progress it to fulfil all your requirements.

• Of course it is too small as an inline graphic. As a PDF Supermarket Data Model.

• The Standard for Relational Data Modelling since 1983 is IDEF1X. For those unfamiliar with the Standard, refer to the short IDEF1X Introduction.

I am using PowerDesigner to create the ERD and then generate everything from it (LDM, PDM, OOM). Is this a bad idea?.

1. PowerDesigner is great. Just ignore the Oracle-specific nonsense, it pushes you into considering the physical far too early.
2. Skip the ERD, it is brain-dead in the context of the Relational paradigm, and surpassed by IDEF1X, which is specific to that paradigm.
   • Use the Entity Level display for ERD equivalence.
3. For small projects you can ignore the academic distinctions {CDM; LDM; PDM; OOM, etc}.
   • There is actually just one model: it is "conceptual" at the beginning, and you just progress to "logical", and last, when the "logical" is stable, to the "physical".
   • Understand that the whole process is Logical.
   • Unfortunately, in PD you have to have separate "models" or files for each.

Now for my main problem It's between these 3 tables:

I have solved that issue. And exposed others.

each customer can request_order from one or more Employee and each Employee can get_order to one or more Customer
each Employee can get_order to one or more Customer

Yes, but that is the overall result. In each shopping or presentation instance:

• a customer can request_order from one Employee (Cashier)
• a Employee can get_order from one Customer

The problem is if I want to know the customer related to that specific order......I can't. How do I fix this?

Solved: Each Order is Identified by (CustomerId, DateTime), ie. the Customer who created the Order.

1. Do not mix Process elements (eg. Get_Order) with Data elements (eg. the data model). The two areas are separate, and governed by quite different science. Here we are solving the Data; only the Data; and nothing but the Data. After that, the Process Model is easy.
2. RecordIds are anti-Relational. They are certainly not needed in a Relational database. Read my other Answers for detailed explanations.
3. Relational Keys (aka Compound Keys or Composite Keys) are standard fare in a Relational database. They provide far more integrity than a RecordId based file ever can.
4. You need to be more precise (state the exact sequence) in defining how an Order is created.

Please feel free to comment or ask specific questions.

I was able to make it run via pyaudio

You should map on cart not cartData:

because onRemove modifies cart