IBD | Interpretable Basis Decomposition for Visual Explanation | Artificial Intelligence library

Yes, data is unencrypted by default.

Prior to MySQL 8.0.16, you have to explicitly set the encryption to enable it, see e.g. for File-Per-Table Tablespace Encryption:

Prior to MySQL 8.0.16, the ENCRYPTION clause must be specified to enable encryption.

which of course implies that if you don't specify it, it is disabled by default.

Since MySQL 8.0.16, the behaviour is inherited:

As of MySQL 8.0.16, the default_table_encryption system variable defines the default encryption setting for schemas and general tablespaces. CREATE TABLESPACE and CREATE SCHEMA operations apply the default_table_encryption setting when an ENCRYPTION clause is not specified explicitly.

By default, a table inherits the encryption setting of the schema or general tablespace it is created in. For example, a table created in an encryption-enabled schema is encrypted by default. This behavior enables a DBA to control table encryption usage by defining and enforcing schema and general tablespace encryption defaults.

but the default value for default_table_encryption is off:

Default Value OFF

Defines the default encryption setting applied to schemas and general tablespaces when they are created without specifying an ENCRYPTION clause.

The default_table_encryption variable is only applicable to user-created schemas and general tablespaces. It does not govern encryption of the mysql system tablespace.

Note that exisiting objects will not be encrypted automatically if you change the defaults, you have to alter them explicitly.

Same issue and same setup - server restart resolved it for me.

mysql user is looking for a home directory, which seems to have not been assigned. To do that, you can execute:

I think what you're after can be achieved very easily in MySQL itself (assuming you are using MySQL):

You should upgrade to MySQL 8.0.

I was working on a system with the same problem as yours. In our case, we had about 1500 schemas per MySQL instance, and a little over 100 tables per schema. So it was about 160,000+ tables per instance. It caused lots of problems trying to use innodb_file_per_table, because the mysqld process couldn't work with that many open file descriptors efficiently. The only way to make the system work was to abandon file-per-table, and move all the tables into the central tablespace.

But that causes a different problem. Tablespaces never shrink, they only grow. The only way to shrink a tablespace is to move the tables to another tablespace, and drop the big one.

One day one of the developers added some code that used a table like a log, inserting a vast number of rows very rapidly. I got him to stop logging that data, but by then it was too late. MySQL's central tablespace had expanded to 95% of the size of the database storage, leaving too little space for binlogs and other files. And I could never shrink it without incurring downtime for our business.

I asked him, "Why were you writing to that table so much? What are you doing with the data you're storing?" He shrugged and said casually, "I dunno, I thought the data might be interesting sometime, but I had no specific use for them." I felt like strangling him.

The point of this story is that one naïve developer can cause a lot of inconvenience if you disable innodb_file_per_table.

When MySQL 8.0 was being planned, the MySQL Product Manager solicited ideas for scalability criteria. I told him about the need to support instances with a lot of tables, like 160k or more. MySQL 8.0 included an all-new implementation of internal code for handling metadata about tables, and he asked the engineers to test the scalability with up to 1 million tables (with file-per-table enabled).

So the best solution to your problem is not to turn off innodb_file_per_table. That will just lead to another kind of crisis. The best solution is to upgrade to 8.0.

Re your comment:

As far as I know, InnoDB does not open tables at startup time. It opens tables when they are first queried.

Make sure you have table_open_cache and innodb_open_files tuned for your scale. Here is some reading:

• https://dev.mysql.com/doc/refman/5.7/en/table-cache.html
• https://www.percona.com/blog/2009/11/18/how-innodb_open_files-affects-performance/
• https://www.percona.com/blog/2018/11/28/what-happens-if-you-set-innodb_open_files-higher-than-open_files_limit/
• https://www.percona.com/blog/2017/10/01/one-million-tables-mysql-8-0/

I hope you are using an SSD for storage, not a spinning disk. This makes a huge difference when doing a lot of small I/O operations. SSD storage devices have been a standard recommendation for database servers for about 10 years.

Also this probably doesn't help you but I gave up on using Windows around 2007. Not as a server nor a desktop.

You can select column names by position or pattern in names or by specifying range of columns. It depends on how your data is structured.

Your two meshes, triangle and quad, have opposite triangle winding order. Here’s how.

By default, D3D11 uses CullMode=Back and FrontCounterClockwise=FALSE. This means it only renders front faces, and front face is defined as “when the vertices are counter-clockwise”.

As you see from the above illustration, your triangle indeed has counter-clockwise order, however both triangles of your quad are clockwise, GPU considers them as back faces and skips both.

You have many ways to fix, any of the following will do.

1. Reorder vertices in vertex buffer.
2. Flip triangles in index buffer to { 0, 3, 1, 1, 3, 2 }
3. Change rasterizer state to disable back face culling, CullMode=D3D11_CULL_NONE
4. Change rasterizer state to switch front face winding direction, FrontCounterClockwise=TRUE
5. Change matrix passed to vertex shader to include mirroring component, e.g. scale with vector [ -1, 1, 1 ] represents a mirror transform that flips X, this will flip winding order of the whole mesh.

You can add more conditions to your existing code. Please note that I just generated a bunch of numbers to get some data.

Windows or not?

Did you restart mysqld?

mv on Linux (and close relatives) is really a "rename". And, assuming the target is on the same filesystem, that rename can even involve a different directory.

When a program (eg, mysqld) has a file (eg, the table partition) "open" mysqld, it has control over it -- even if you run off to a shell and rm the file!.

I suspect that when you restart mysqld (for any reason, including reboot), the "data directory" will become messed up.

Aside from the filesystem's partitioning, you must tell MySQL when you "archive" a partition. Read up on "transportable tablespaces" for the version you are using. Here's a writeup for 5.6; 5.7 has some improvements.

I don't see the advantage of using a filesystem partition. With "transportable tablespaces", you can disconnect a MySQL partition from a PARTITIONed table. This turns the partition into a table. Then that table can be deleted, renamed, copied, etc, without impacting the partitioned table. Search for "transportable" in http://mysql.rjweb.org/doc.php/partitionmaint ; there are some links.