Description
There is no possible way to get Table data for another DB and another file namespace.
Problem 1 - DB
Table class doesn't let you use different database connection. Neither the DB class.
Problem 2 - Files
So I can't access, using TableFiles::class, files from another project, even if they are on the same server.
That's because different projects use different file namespace, inherited from PSR-4 project classes namespace.
Feature 1 - DB
Let Table specify another database connection, using the key from config/databases.json file.
Feature 2 - Files
Let the Arshwell user specify the file namespace. It should be an optional field. By default it will be used the current project namespace.
For a better usage, make all table files classes extend the same abstract class named: AbstractFile::class.
Example
For DB
class User
{
const DB_CONN_KEY = "[conn-key]";
}
For Files
class User
{
const FILESTORAGE_KEY = "[storage-key]";
}
Arshwell Version
0.*
Description
There is no possible way to get Table data for another DB and another file namespace.
Problem 1 - DB
Table class doesn't let you use different database connection. Neither the DB class.
Problem 2 - Files
So I can't access, using
TableFiles::class, files from another project, even if they are on the same server.That's because different projects use different file namespace, inherited from PSR-4 project classes namespace.
Feature 1 - DB
Let Table specify another database connection, using the key from config/databases.json file.
Feature 2 - Files
Let the Arshwell user specify the file namespace. It should be an optional field. By default it will be used the current project namespace.
For a better usage, make all table files classes extend the same abstract class named:
AbstractFile::class.Example
For DB
For Files
Arshwell Version
0.*