How can I alter database bundles such as compression or any other bundle through Raven Studio or even via code?
You can modify them via the Database Settings, note that this is typically not a supported operations.
You can do that via the Raven/ActiveBundles settings.
Related
I have a Vaadin Flow app that accesses an Azure SQL database that keeps shutting down and restarting. Upon further investigation, I discovered that Hibernate is trying to drop and recreate database tables because it is using an H2 embedded database, which I do not want. After reading the documentation, I determined that I can turn this feature off by setting auto-dll to none in either hibernate.cfg.xml or application.properties or application.yml. The problem is that none of these files exist on my local machine, and I can't find them on my cloud drive either. How can I stop Hibernate from dropping and recreating my database tables?
The file was located in src/main/resources. It doesn't show up in a Windows search, not even if I search for system files.
I am on Apex 5.1 in a hosted environment and have an application that uses a custom LDAP authentication function. It works fine when the application is running on the Production schema. I now wanted to make some changes to the schema and application, so our hosting vendor added a 'DEV' schema on same instance with exactly the same data and objects as PROD and I then exported the application and used the DEV schema as the parsing schema when I imported it back to same Workspace so I could make changes to the application without touching prod data. This set up works fine when I use the Application Express authentication and go ahead and make changes to the DEV schema and to the application, but when I try to test my changes using the custom LDAP authentication, I am getting Invalid Session thrown by DBMS_LDAP. Since both schemas are on the same oracle server, I assumed that the same LDAP function that works in PROD schema should work with the DEV schema. Looking at the custom LDAP function, there is no reference to schema owner so what am I missing? I would have assumed identical functions should function identically against the same Oracle server even though coming from 2 different schemas. Does my hosting vendor need to make sure ACLs for both schemas (PROD and DEV) are identical??
Thanks,
Pat
My guess was correct. ACLs were not set identical for both schemas. Once ACLs were adjusted, LDAP worked as expected.
I'm changing a value in the advanced settings of the CMS, specifically the ProviderTypeName of Blogs -> Providers -> OpenAccessDataProvider
However, when rebuilding the site the setting is reverted to its default.
I believe this is happening because the property is stored in a file, and my build and deployment is overwriting it with whatever is in my repository.
Where is this setting stored in the file structure; or if I'm way off base in my assumption, how do I get this setting to stick?
You right, most probably you overrode configuration changes during the deployment. Most of the time, I am excluding all configuration during website deployments and from VS project.
By default, Sitefinity 10 is using a hybrid mode that stores configuration files on both the file system App_Data/Sitefinity/Configurations and the database in table [sf_xml_config_items]. Documentation: https://docs.sitefinity.com/auto-storage-mode-of-configurations
Also, there is a way to move configurations to database only: https://docs.sitefinity.com/database-storage-of-configurations
I wonder if there is a good way of deploying database changes made on a typo3 website (on dev) to a live website?
In Magento for example there are folders containg sql install statements (for the structure, new tables etc.) and data install scripts (inserting data into the tables).
These scripts are automatically executed when deployed to live.
Good ways of getting rid of manual database adaptions are welcome.
Thanks!
cweiske explained it well, for common admin it's enough to know that Install Tool has Database Analyser > Compare functionality, which is dedicated for handling DB schema differences.
TYPO3 extensions have their ext_tables.sql files which define the database structure they need.
When installing the extension, the necessary database structure changes are made by the TYPO3 extension manager. You can also apply the changes yourself by using the install tool -> database update.
So as long as your extensions have the correct table definitions, you're fine and can rely on TYPO3 to update the actual database.
Added RavenDB add-on to AppHarbor app.
It seems that creating databases is disabled in the RavenDB admin.
Why?
You should already have had one created for you, the connectionstring is injected into your configuration file with the name RavenDB. Details here: http://support.appharbor.com/kb/add-ons/using-ravendb-and-ravenhq
I believe they use the multi-tenant support to separate each customer, so you have a single database created for you when you add the addon.