One line description of the issue

Python script

DATABASES = {
    'default': {
        'ENGINE': 'djongo',
        'NAME': 'your-db-name',
        'HOST': 'your-db-host',
    }
}

should be

DATABASES = {
  'default': {  
    'ENGINE':   'djongo',
    'NAME':     'yourmongodb',
    'CLIENT': {
  

This is a suggested addition to the Micronaut-Data docs on @transactional. Please consider adding this note to section "6.1 Transactions":

NOTE: The javax.transaction.Transactional annotation is only supported in repositories and beans processed by Micronaut. Using @transactional on other methods/classes does not initiate a transaction. See "Programmatic Transactions" for hints on how to use

• Theory: explain difference to simple keys
• Tutorial: add compound keys
• Technical documentation?
• Use dm_nycflights13(compound = TRUE) in some documentation
• Double-check consistency
  • References to weather table
• Blog post

A user asked if we had an official spec for the format of the mappings.json file that’s created. Might be something helpful for users to know the layout so they can better adjust and edit it.
https://twitter.com/ta_o_zi/status/1224897034680881154

This is a bug | feature request.

Prerequisites

• Are you running the latest version?
• Are you reporting to the correct repository?
  (enso is made of many specialized packages: https://github.com/laravel-enso)
• Did you check the documentation?
• Did you perform a cursory se

Each external store could have a default download path to be specified in its config so whenever attachments are fetched and downloaded they automatically go into the right default folder. This path could be overridden by passing the "download_path" keyword argument to ".fetch()"

Add methods to explore the modeled parameters after modeling.

SDV should have a visualize or explain or view method to obtain details about the parameters learned during the modeling.

When possible, information should be obtained at a column level (univariate distribution) and at a table level (mutivariate distribution).

API and implementation details will be further discussed in th

• implement a documentation generator based on module's information
  • generate for 1 module
  • generate for all available modules
• implement workflow to keep this documentation updated
  • eg: by generating the docs and attaching them to some markdown file when a new version is about to be released

Screenshot of the mouse over the icon:

This should show some valuable information in the tooltip or not show the tooltip at all.