persona | Opinionated user management service for AdonisJs | Runtime Evironment library

I have the following two tables:

claims_tbl

I want to add a column (type) to my metadata table that lists what type of sample it is based on information from the id column.

I am trying to define a type where the favoriteFruit property's value must be an item in options array. Where the options array is dynamic/unknown (making it impossible to use union types "|").

I have the following table:

I have created a ggplot graph, with ggmap() and geom_sf(), but when I try to visualize it with ggplotly() there are some elements that are not translated.

1. It seems that the labels when using scale_fill_manual() are not interpreted by plotly.

2. In addition, the labels must be formatted, as can be seen in the graph generated by ggplot, and modified as established in ggplot with the labels argument of scale_fill_manual().

3. The labels should be positioned on the colored boxes. Also as you can see in the graph generated with ggplot.

4. The frame that adds plotly seems unaesthetic to me and I would like it not to be shown.

5. The subtitle shown with ggplot2 cannot be found in the plotly generated graph.

6. Is it possible to hide the menu (download, zoom, ...) plotly from the graphics?.

7. Finally, in a different vein, I have tried to add information to each area of the graph, when hovering the mouse, but it does not show anything, only the value of the variable geosmunicipios$Renta.media.por.hogar.2016.quantile, which was already displayed by default, using hoverinfo() in ggplotly().

8. It only shows the default text that I have indicated in point 7 by hovering over the lines of the polygons but not in the area of the polygons.

In short, the ggplotly graph should look as close as possible to the one generated with ggplot2.

The file for download is available at: https://www.dropbox.com/s/9nmy0uj00jhc1y4/geosmunicipios.R?dl=0

Here's the gist, I'm using Django to fill a PostgreSQL database to store user data from a third-party API. I'm using an API to get the data into Django so that I can automate the filling of the DB. I have the models built for the fields that need stored.

Here's where I need some help. I've create a list from an API response but I want to remove duplicate users and combine the lists, like this.

I have the parent table "persona"(people), which child tables "clients" and "treballadors"(workers) inherit from. I inserted one row in each child table. I also have a table, "passis"(cards), which is related with "persona" 1-1. Not all persons have a card, but all cards belong to a person, so the cards table receives the foreign key. However, when I try to insert a row into the table, the following foreign key-related error triggers:

As you can see, a record in table persona with id=2 is actually present. Why then the error?

This is how table 'passis' looks like:

I am making two calls from API with Axios, it works and it brings me the two results I need, the problem is that I want to iterate through my first Axios call, but It says:

Forgive me if this has been answered elsewhere. I've been searching SO and haven't been able to translate the seemingly relevant Q&As to my scenerio.

I'm working on a fun personal project where I have 4 main schemas (barring relationships for now):

• Persona (name, bio)
• Episode (title, plot)
• Clip (url, timestamp)
• Image (url)

Restrictions (Basis of Relationships):

1. A Persona can show up in multiple episodes, as well as multiple clips and images from those episodes (but might not be in all clips/images related to an episode).
2. An Episode can contain multiple personas, clips, and images.
3. An Image/Clip can only be related to a single Episode, but can be related to multiple personas.
4. If a Persona is already assigned to episode(s), then any clip/image assigned to the persona can only be from one of those episodes or (if new) must only be capable of having one of the episodes that the persona appeared in associated to the clip/image.
5. If an Episode is already assigned persona(s), then any clip/image assigned to the episode must be related to aleast one of those personas or (if new) must only be capable of having one or more of the personas from the episode associated to the clip/image.

I've designed the database structure like so:

This generates the following sql: