Description

Changes:

• Model can query sql in project to get data to model. It means that user can use project name as database
  • CREATE MODEL model FROM mindsdb (SELECT * FROM example_db.home_rentals) PREDICT rental_price;
• integration name is optional for create/retrain/finetune. It is possible to create model without database specified. Current project will be used
  • CREATE MODEL model FROM (SELECT * FROM example_db.home_rentals) PREDICT rental_price;
• It is also possible to use LAST in these commands:

retrain home_rentals_model1 from (
  select * from my_pg.home_rentals where id>last
) 

Side feature: second context for conditional job
It will allow to run job like this, when we have LAST in both conditional and execution blocks

create job j1 (
    FINETUNE MODEL home_rentals_model
    FROM (     
        select * from my_pg.home_rentals where id>last
    )
)
every 1 min
if (
    select * from my_pg.home_rentals where id>last
);

It creates second 'job-if' context to not change 'job' context and not hide new data from job.

Dependent on mindsdb/mindsdb_sql#373

Please include a summary of the change and the issue it solves.

Fixes #9051

Type of change

(Please delete options that are not relevant)

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ⚡ New feature (non-breaking change which adds functionality)
• 📢 Breaking change (fix or feature that would cause existing functionality not to work as expected)
• 📄 This change requires a documentation update

Verification Process

To ensure the changes are working as expected:

• Test Location: Specify the URL or path for testing.
• Verification Steps: Outline the steps or queries needed to validate the change. Include any data, configurations, or actions required to reproduce or see the new functionality.

Additional Media:

• I have attached a brief loom video or screenshots showcasing the new functionality or change.

Checklist:

• My code follows the style guidelines(PEP 8) of MindsDB.
• I have appropriately commented on my code, especially in complex areas.
• Necessary documentation updates are either made or tracked in issues.
• Relevant unit and integration tests are updated or added.