Is there a way to get savepoint support in a Zope connection to Postgres?
I'm currently using ZPsycopgDA, which doesn't support savepoints, and is also hard to install with buildout. Would switching to something like SQLAlchemyDA make things easier?
Background: I've got my users in a postgres database, but when I try look at the history, I get errors about savepoints. That problem is explained here: http://plone.org/products/cmfeditions/issues/46
I would recommend asking in the Plone forums: http://plone.org/support
I'm not using much relational databases myself, but in general you can use collective.tin and other integration products that hook up SQLAlchemy to Plone for content, or if you want to store everything in a relational database, look at RelStorage.
It turned out that SQLAlchemyDA does seem to support savepoints - at least when I switched to it, it did fix the issue.
Related
I am trying to migrate database from oracle 11g to MySql 5.7, after the migration what are the issues i might find ?. How triggers, sequences, privileges etc are supported ?. Any performance issues ?. I need to report these pros and cons before migrating from oracle to MySql. Please help me to report, i didn't find any solution in google related to this, anyone please help.
Despite the ANSI SQL standard every DBS has its own specialties.
All your Questions are so much depending on your specific DB structure, code and functions you've used, nobody can give you clear answer.
You can run in all the Problems you are asking or into none of them.
If your current Oracle DB application is 100% ANSI SQL it should at least run, but i doubt it will be 100% ANSI SQL.
The only possible answer is try it, see what Problems you are facing and then decide if you want to do it or not.
I’m using EE for the first time. I design/develop on two machines, so I use private github repos for all my client work. I’d like to run this EE project on SQLite locally while I’m developing and designing, and then switch it to MySQL once I’m ready to deploy to the staging environment for client review. That way, I can track DB changes easily between machines, as there is a lot of content on this particular site, and exporting/importing DB tables every time I switch machines (three or more times a day) is getting old.
I realize I could use the client’s MySQL DB remotely, but would rather keep everything local, if at all possible. So, how can I run EE with SQLite?
This question (or something similar) was made almost three years ago here. The accepted answer hints at possible support in EE v2.0+ (via CodeIgniter’s then-new database abstraction), but I can’t find any recent information (official or otherwise) on how to make it happen.
I short: no. Active Record is not universally-used throughout EE, and especially not in third party add-ons. In fact, the documentation for the Database class does not mention Active Record at all.
I'd suggest just installing MySQL locally.
I don't think you'll have much luck with non-MySQL DBs — MySQL statements are hard-coded into EE, despite the EE 2.0 promises of a fully-fledged CI app with various DB connectors.
I think your best results might be to find a centralized host for your dev DB. EE is especially painful to work with on multiple machines because of the DB — the whole thing is really built with "one server, one developer" as the primary use case.
You can simplify it a bit by keeping your templates saved as files, and rigging your settings to be server-agnostic. I also keep little scripts around to quickly dump/import the DB when I have to, which makes moving the site around in a git repo a little easier. A few details here: http://www.viget.com/inspire/expressionengine-on-multiple-machines/
We are a software development company and are using Wordpress for static portion of the web site. Naturally, all our workflow is built around version control: multiple developers -> continious integration -> staging -> deployment.
Our challenge with integrating Wordpress into our workflow is that its database is stuck like a bone in the throat: you cannot put it into the version control, easily roll back, promote from staging to production etc.
I am wondering what people do in similar situations? I would like to find a way to integrate WP into the development workflow and not the other way around :-)
Clarification we want to "develop" and test pages on the staging system and when ready then move them over to the production as part of the version upgrade process. We don't want to do full replication of the staging database to production.
That's a common question and one that I've worked on tackling. I've written some code to address these issues albeit the code's not ready for distribution. Basically the idea is to create scripts to import the content and then version control the scripts. (Actually my approach uses a custom import/export format designed to be easy to hand-modify, but the idea is similar.)
Anyway, there are some related questions over on StackOverflow's sister site WordPress Answers:
Questions tagged with the term [staging]
Questions tagged with the term [deploy]
UPDATE
Per the clarification, this would probably be helpful too:
Is there any way to draft a revision of a published page or post? What workarounds have you used?
Hope this helps.
-Mike
I've just hit the same problem. For now we are using MySQL dump files to export/import database content, but it gets ugly with several people working on the database changes.
Since the team that works on the project is all internal and consists of just a few people, I'm thinking into the direction of locking the database dump file in VCS. Subversion had this functionality built-in, but we are using git, which, I think, is conceptually opposite of any kind of locking.
Probably we'll have a workaround script with pre-commit hook to check for the existence of a lock file next to the dump. The person who committed the lock file will be the only one allowed to commit the dump. Once he finishes the work, he will need to commit the removal of the lock file.
It sounds ugly, I know. But I've thought about it for a while and don't see an elegant solution yet.
If you're only using WordPress for static content, then any tool/methodology for version controlling databases should work - for example, work the mysql command line tools into your CI and deployment routines.
we have a team and want to make a site using drupal.
as i see all the changes will be saved in database. so how we can have a version control?
should we use of a cvs that take care of databases?
if yes, how can i make a db cvs server?
thanks.
Yes, use git. As far as the database goes, you're best off using update hooks to capture schema changes in code. If you're using cck you're not going to be able to do that reliably. It's a bummer really.
http://api.drupal.org/api/function/hook_update_N
to port views, content type, contexts you can use http://drupal.org/project/features
Devel http://drupal.org/project/devel have tool to make record macros
But realy there is no universal tool for this.
You should utilize Git for team development work for code.
As far as version controlling a database, you are not going to want to do that. It is a lot of headache.
You can move a lot of the stuff that normally goes in the database into the code instead. If you use the strongarm module along with the features module you can save settings, content types views and much more as code and put it into your VCS.
I would like to find out if there is wiki software that runs on SQLite.
Sure is.
Instiki
Instiki (What Is Instiki) is a basic
Wiki clone so pretty and easy to set
up, you’ll wonder if it’s really a
wiki. Runs on Rails and focuses on
portability and stability. Supports
file uploads, PDF export, RSS,
multiple users and password
protection. Some use Instiki as a CMS
- Content Management System because of its ability to export static pages.
Fossil, which is a DVCS with many other features (including a wiki) is built on top of Sqlite (in face, made by D. Richard Hipp who wrote Sqlite ). It can be found at: http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki
According to the SQLite Users Page, the CVSTrac program is using SQLite as its internal database structure (you have to follow the link to the CVSTrac site to see the details). I'm sure there are others by hunting around the site.
Wiki::Toolkit can use SQLite as its database.
Mediawiki does, but it is only in the development stage.
Any of the Django ones should be able to, because Django is flexible about which Database backend it uses and SQLite is one of the options.