Generic update of “normal” columns with data from JSON

I am trying to do a "generic" insert/update of table columns using JSON. There are tons of info how to update a JSON column, but I have found none that updates several normal columns in a table generic.

Insert columns with JSON data works

This works as I understand it in a generic way:

INSERT INTO inputtable SELECT * FROM json_populate_record (NULL::inputtable,     '{       "id": "0",       "name": "orkb type foo examples tutorials orkb",       "sum": 5743,       "float_col": 94.55681687716474     }' ); 

Fiddle: https://www.db-fiddle.com/f/eaQG8H4yqY9hnQBZjzJgz/29

Update columns with JSON data?

There are examples of "non-generic" update using JSON, but I am searching for a "generic" solution. In my dreams it should work as this pseudo code:

with data as ( select * from json_each_text(     '{       "id": "0",       "name": "orkb type foo examples tutorials orkb",       "sum": 5743,       "float_col": 95     }') ) update inputtable set = (select * from data) where id=0 

Is this possible to do? If it is, how do I do this?

Google Analytics GA4 – How to filter data based on Event parameter values

I am very new to GA4 and have been working with Universal analytics for the past 2 years. Now custom events are tracked in my GA4 property along with Event parameters and custom dimensions. But where can I filter an Event using the event parameter data ? Like in Universal Analytics we have an advanced option on the right corner on top of the result table, where we can filter based on "Category/ Action/ Label or dimensions". How can I do the same in GA4 ?

Below is the the filtering options used in UA :

enter image description here

GA4 funnel exploration won’t display known data

I am using a funnel exploration in GA4 to map customer journeys from Google Search Ads through my company’s e-commerce site. The funnel begins with "session_start" and ends with "purchase," and there are several custom events in between.

A few weeks ago, the funnel stopped displaying any data for the "Paid Traffic" segment, and gave the message "No data for this combination of segments, values, filters, and date range."

I know from the Search Console that we are getting clicks on our ad, and I know that GA4 is recording the events on our site, because I can see them in the path exploration. However, looking at the same segment over the same date range in the funnel exploration gives the error above. I changed the funnel to just display the number of users that started a session on our site, and am still getting a message that there is no data. I have attached screenshots of the path exploration as well as the abbreviated funnel.

path_exploration empty_funnel

I’m wondering if anyone would have any insight into why the funnel would have stopped populating. I have posted on the Google Analytics Help forum with no success, and Google doesn’t seem to have much in the way of support for GA4. I have tried expanding the date range from what is shown in the screenshots to include more data, with similar results. Any help would be greatly appreciated!

MySQL Table structure and data export – Script sequence is not correct

When I export the data and structure of my MySQL database to a file, I notice that the table sequences in the output file are not correct. For example the script of a child table is put before the master table. Incase of MSSQL that is not the case. Any idea how that can be corrected?

MySQL80 MySQL Workbench 8.0

Structured data for category pages

We run a wordpress website. Our category pages are a but different from the standard category pages. They are articles in which clusters of underlying articles are presented with some surrounding content. the links to the articles are subcategorized. I understand that "collectionpage" is the right page type and itemlist (OR haspart??) containing the references to the different articles.

My question: should I use separate itemlists for the articles per subcategory or throw all the articles referenced on the categorypage in 1 itemlist?

t

Msg 8114, Level 16 , State 5, Line 1 Error converting data type nvarchar to float error

Just having some issue when trying to combine table using the union function keep getting this error as above

Msg 8114, Level 16 , State 5, Line 1
Error converting data type nvarchar to float error

SELECT * FROM dbo.['202004-divvy-tripdata$  '] UNION ALL  SELECT * FROM dbo.['202005-divvy-tripdata$  '] UNION All SELECT * FROM dbo.['202006-divvy-tripdata$  '] UNION all  SELECT * FROM dbo.['202007-divvy-tripdata$  '] UNION all SELECT * FROM dbo.['202008-divvy-tripdata$  '] UNION all SELECT * FROM dbo.['202009-divvy-tripdata$  '] UNION ALL SELECT * FROM dbo.['202010-divvy-tripdata$  '] UNION ALL SELECT * FROM dbo.['202011-divvy-tripdata$  '] (UNION ALL SELECT * FROM dbo.['202012-divvy-tripdata$  ']) -----> here is where it stops working and I get an error message as shown above.  

Can I get help on this?

Submit a form and save data to custom post type in woocommerce

I am wondering how can I send the data submit in WS FORM to a tab in WooCommerce Frontend Manager the tab have his own php but the site is multivendor.

wsform gave this action config im triyng using Push to Custom Endpoint: http://localhost/vendor/tabpage.php and requested method:post

<?php 

$ vendor_id = $ store_user->get_id(); $ $ wcfm_modified_endpoints= get_user_meta( $ vendor_id, ‘wcfm_endpoints’, true ); ?>

echo do_shortcode( ‘[wcfm_store_info data="ws_form id="2"]’ );

Recovering InnoDB database from backed up “data” folder in XAMP in Windows 10

I copied the data directory from mysql folder and uninstalled the XAMPP as the MariaDB was not starting. I installed XAMPP same version and backed up the data folder into mysql data directory. At first only copied the required database folder named production inside the mysql data directory. PhpMyAdmin showed the tables correctly though no record/row was there and it showed "Table doesn’t exist in engine". Then I copied all the contents from the DATA folder to the mysql data folder and now it does not start. Now the problem is MariaDB is not starting. I tried setting the innodb_force_recovery but it failed to start the mysql.

The error log is given below:

2021-06-11  0:08:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2021-06-11  0:08:23 0 [Note] InnoDB: Uses event mutexes 2021-06-11  0:08:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-06-11  0:08:23 0 [Note] InnoDB: Number of pools: 1 2021-06-11  0:08:23 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-06-11  0:08:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M 2021-06-11  0:08:23 0 [Note] InnoDB: Completed initialization of buffer pool 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\applied.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`applied``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`applied` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\data.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`data``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`data` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\data_employer.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`data_employer``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`data_employer` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\education.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`education``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`education` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\education_list.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`education_list``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`education_list` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\industry.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`industry``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`industry` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\jobs.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`jobs``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`jobs` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login_admini.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login_admini``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login_admini` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login_employer.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login_employer``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login_employer` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\resume.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`resume``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`resume` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\selected.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`selected``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`selected` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\entries.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`entries``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`entries` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\geoname.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`geoname``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`geoname` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\geonamebackup.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`geonamebackup``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`geonamebackup` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\pincodes.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`pincodes``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`pincodes` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\specifier.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`specifier``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`specifier` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\users.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`users``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`users` because it could not be opened. 2021-06-11  0:08:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2021-06-11  0:08:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-06-11  0:08:23 0 [Note] InnoDB: Setting file 'D:\Program Files\XAMP\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-06-11  0:08:23 0 [Note] InnoDB: File 'D:\Program Files\XAMP\mysql\data\ibtmp1' size is now 12 MB. 2021-06-11  0:08:23 0 [Note] InnoDB: Waiting for purge to start 2021-06-11  0:08:23 0 [Note] InnoDB: 10.4.19 started; log sequence number 1515509790; transaction id 611499 2021-06-11  0:08:23 0 [Note] InnoDB: Loading buffer pool(s) from D:\Program Files\XAMP\mysql\data\ib_buffer_pool 2021-06-11  0:08:23 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-06-11  0:08:23 0 [Note] Server socket created on IP: '::'.