Group | 轻量级框架 。实现了定时任务功能，分布式任务队列，命令行控制台，数据库脚本自动化，单元测试 , rpc服务，多进程服务 | Application Framework library

I thought that in your situation, it is required to retrieve 6/17 from 06/17/2021. For this, how about the following modification?

In this case, please modify doPost as follows.

Convert your dates with to_datetime then subtract from today's normalized date (so that we remove the time part) and get the number of days. Then use pd.cut to group them appropriately.

Anything in the future gets labeled with NaN.

There are two approaches that are possible. The first is to use a suborchestrator for each job so that each suborchestrator handles just a specific job. Here is the docs for this approach https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-sub-orchestrations?tabs=csharp Example from docs seem to be alike to yours.

The other is to use ContinueWith so that each job has its own "chain"

Since, I am not 100% sure the context in which you are trying to apply the MVC pattern, a good generic explanation of MVC can be found in GoF's 1995 book, Design Patterns: Elements of Reusable Object Oriented Software.

In the book, they state the following.

The Model is the application object, the View is its screen presentation, and the Controller defines the way the user interface reacts to user input.

A more robust explanation can be found from Martin Fowler where he also makes the case for a variation of Model View Controller that uses a Presentation Model.

If you are referring to Spring MVC then there is some magic that blurs the lines a bit. But in general, you have a controller that represents some screen or an encapsulated piece of functionality that the user (web requests) interact with. The controller serves up responses that are derived from the domain, usually via a Spring Service (i.e. @Service). The domain (Model) doesn't know anything about the View and the View may or may not know anything about the domain.

Given that, the View should be derived from the Model. But that's not always the case since sometimes how we present things to a screen is not the best logical way to model things in our domain - not to mention, the domain should be presentation agnostic. This leads into Fowler's argument for a Presentation Model, which is a model that belongs to the Presentation.

I call this a Presentation Model because it's a model that is really designed for and thus part of the presentation layer.

Microsoft took that idea and ran with it in a variant of MVC called MVVM (Model View ViewModel).

You can read more about that in Microsoft's documentation on ASP.Net Core.

So, back to your original question of "Should you pass the model directly to the view?" If you are using MVC then the controller is what provides the interaction. But if you're really asking, "Can you bind your view directly to the model?" If your model has all the stuff you need organized how your view needs it, then sure. And if it's simple enough, maybe that's the way to go. Otherwise, you could go with something like a Presentation Model or MVVM.

For columns with only strings, you can use pandas df.equals() that compares two dataframes or series (cols)

A good justification for the name is that lets say you have a naming convention to your files and for components.

For example if all components are named with what they are but not appended with comp (ie: Inventory.vue instead of InventoryComp.vue) and when you use them you want to be more explicit about what they are (components) so you want to use this component like this: . An easy way to do this is to use the name property and set it like this in your Inventory.vue:

By default laravel thinks that id is the primary key in your table. To fix this you would have to a primary key variable in your model

So, this is a good opportunity to use purrr::map. You are half way there by applying code to one dataframe.

You can take the code that you have written above and put it into a function.