Hi,
It appears this is an odd MySQL bug as discussed in detail here:
https://bugs.mysql.com/bug.php?id=42041
Have you tried increasing your table_definition_cache setting? Increasing this value appears to have solved the problem for many users found both in the above discussion and on Stack Overflow.
Hi,
To get more verbose logs there are a couple of options. To see everything happening across your instance you can enable debug in your .env file. For a full tutorial please reference our guide here.
To avoid getting locked out of your instance we recommend enabling email support upon installation of DreamFactory. This will allow you to take advantage of the “Forgot Password” button on login. Our Guide has a handy section on this specifically: “Enabling Email Registration”
If you are already locked out of your instance and you are running a Bitnami install there is a possible workaround that can be used as a last ditch effort. This would require you logging in to your system database and deleting all users you have created. Once deleted you can go back to the browser and you should be redirected to create your first Admin.
Hi Christian. Thank you for your question.
You are right. You will need to create a service each for the each of the SQL databases. That being said, a lot of DreamFactory customers use the Data Mesh feature wherein you can write your scripts in Node.js, V8js, or PHP, with more languages on the way. Server Side Scripting provides a simple way to modify the request or response of any API call. So one easy way to combine multiple data sources is to add some fields to a record when the data is returned. Ref
To see a tutorial on Data Mesh in DreamFactory, check out this video - https://youtu.be/6yOH1w2hjxM
Please feel free to reach out if you have any more questions.
Abhishek
@jason.gilmore
We can close this issue.
Hi Jose.
Were you able to solve this issue? To get started with connecting MYSQL with DreamFactory, refer this short video - https://youtu.be/FPoXJLK1wkw
Please let us know if you have any questions. We are here to help
Hello @Kaustubh_Kadam.
Via postman are you passing the request body as JSON?
May I know how you are calling the JsonObjectRequest in your android code? If you can post a snapshot of your code, I can have a look at it.
Thanks
It is possible to fetch more that 1000 records at a time. The default setting (1,000) is in place so users do not accidentally call an exceedingly large number of records with a single call, and potentially crash a browser or other client.
You can change this setting on a case-by-case basis by navigating to the API configuration within your DreamFactory administration console, and changing the Maximum Records setting accordingly. To override the default globally open the .env file and modify the DB_MAX_RECORDS_RETURNED setting (be sure to additionally uncomment the line by removing the preceding hash mark (#). The .env file resides in your DreamFactory application’s root directory. To identify the root directory, click on your Config tab and consult the Install Directory path.
After saving the file be sure to clear your cache to ensure the changes are picked up. You can do so by executing the following command from within your DreamFactory root directory:
$ php artisan cache:clear && php artisan config:clear
Swagger errors can arise from a variety of situations. The most notable error would be due to the use of an incorrect Swagger specification. The DreamFactory 2.10 release updated Swagger support to accommodate version 3 (also, Swagger was renamed to Open API with the version 3 release). Therefore if you’re still running a DreamFactory version older than 2.10, you’ll need to use a Swagger 2.X-compatible specification. If you’re running 2.10 or newer, then you’ll need to use an Open API 3.X-compatible spec.
Another commonplace issue is an invalid specification. You can validate your Open API document using https://validator.swagger.io/. If you’re writing a specification, we suggest using a tool such as Spotlight Studio.
Hello @bhavna.lintel
The applicationAPIKey is used to consume DreamFactory APIs. Each app has a unique API key that is sent with each request. When no session token is provided, the request is considered to be from an unauthenticated user and the system uses the API key to look up the default role for the app. The API can be generated in the DreamFactory dashboard.
More information on creating an app and generating API keys can be found here on DreamFactory guide
Let us know if you any more questions
Based on the given information I assume you are running DreamFactory version 2.12 and with the release of MySQL 8 it introduced some new security protocols that created compatibility issues with PHP 5.6. This has all been sorted in new releases of DreamFactory as we now require PHP 7 to run the application.
Alternatively, since MySQL 8 default authentication plugin is auth_socket you can change it to the original native password authentication. The command below will change the user you are connecting to DreamFactory with to utilize standard authentication.
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password
BY 'password';
As a side note, if you would like this change to be made global for all your MySQL users you can edit the MySQL my.cnf file and under the mysqld section add the following:
[mysqld]
default_authentication_plugin= mysql_native_password
and be sure to flush the privileges:
FLUSH PRIVILEGES;
A great article has been published on this error particularly. In summary, the error is caused by PHP is trying to delete the session files while this is also being done by a cronjob put on the system by the Debian package maintainers of PHP.
The easiest solution is changing the permissions which is typically www-data:www-data.
chown -R www-data.www-data /var/lib/php5
Hello @andres81
Sorry for the delay in our response. The Bitnami virtual machines include everything you need to begin running DreamFactory and include a built-in database server, web server, PHP runtime, and a bunch of other useful software.
If the issue still persists, I recommend doing a clean install of DreamFactory. https://bitnami.com/stack/dreamfactory/installer
Thanks
This is happening because of the CORS (Cross Origin Resource Sharing) . For every HTTP request to a domain, the browser attaches any HTTP cookies associated with that domain. This is especially useful for authentication, and setting sessions. You are doing an XMLHttpRequest to a different domain than your page is on. So the browser is blocking it as it usually allows a request in the same origin for security reasons. You need to do something different when you want to do a cross-domain request.
JSONP ( JSON with Padding ) is a method commonly used to bypass the cross-domain policies in web browsers. You’re on domain example.com , and you want to make a request to domain example.nett . To do so, you need to cross domain boundaries. JSONP is really a simple trick to overcome the XMLHttpRequest same domain policy. So, instead of using XMLHttpRequest we have to use < script > HTML tags, the ones you usually use to load JavaScript files , in order for JavaScript to get data from another domain.
Localhost
If you need to enable CORS on the server in case of localhost, you need to have the following on request header.
Access-Control-Allow-Origin: http://localhost:9999
Hi @sman
Sorry for the delay in our response. In order to generate open API docs for your third party integrations, you can either request the third party to generate them for you or you can use an application like https://stoplight.io/ which can be used to create and manage open API docs.
Hope that helps.
Thanks
Hi Guys!
I’ve been migration my DF from 2.0 to 4.0 and today the tests were started. When the APIs call a table it’s ok, but when call a function or procedure there are differences in response.
For example
Case 1
I call the API in DF 2.0, and receive an HTTP 500 with an error, and in DF 4 I received HTTP 200 with an empty response.
Case 2
I call the API in DF 2.0, I received a full message, and in DF 4 I received HTTP 200 with an empty response.
Why these differences and how to resolve them?
Hi,
I’m getting the error “Use of undefined constant OCI_CRED_EXT - assumed ‘OCI_CRED_EXT’ (this will throw an Error in a future version of PHP)” when access the Schema Manager and in the log’s I’m found the error below…
[2020-04-14T20:34:43.583338+00:00] local.ALERT: Failed to include service: XXXXX in manifest due to error:Use of undefined constant OCI_CRED_EXT - assumed ‘OCI_CRED_EXT’ (this will throw an Error in a future version of PHP)
Any suggestions to solve this error?
This issue seemed to have been isolated to Firefox browsers and not passing the utf-8 header properly. We have not had any similar reports of this issue on more recent versions of Firefox and DreamFactory.
Hi,
This issue is due to the ORACLE_HOME and LD_LIBRARY_PATH environment variables not being properly set. The DreamFactory wiki contains detailed Oracle installation and configuration instructions:
http://wiki.dreamfactory.com/DreamFactory/Installation/Databases/Oracle_DB
Although this post is several years old it receives quite a bit of traffic so I wanted to provide some additional input regarding PostgreSQL configuration. When configuring a new PostgreSQL API you’ll supply the database’s hostname/IP address, database name, username, password, and finally the desired schema (see screenshot).
These 5 fields are required, however you also have quite a few additional options for tweaking the API’s behavior. Among other things you can override default driver options, the default timezone, define the character set, and enable caching.
