Recently I was working on a project where I am supposed to capture data change on a postgres db to update a cache.
After some search i found that i could use Embedded-Debezium to detect all changes on the data base.
In order to ensure the communication between debezium and postgres db , I need to install a logical decoder output plugin to deliver data as Protocol Buffers
postgres-decoderbufs-output-plugin
The link above showing how to install the plugin into Pg installed on a linux distributions..
I wonder how to install it for PG installed on a windows machine?
Is there any other options to integrate debezium with PG wihtout using this plugin?
The Postgres Debezium logical decoding plugin is not available for windows is not available yet you have to build it by your self.
Related
When attempting to create a Strapi App which is connected to a MongoDB cluster and selecting the custom installation, all online tutorials suggest that "mongodb" should be one of the options in the dropdown list alongside "postgres", "mysql" and "sqlite". However, I am not getting an option for mongodb.
I have tried reinstalling nodejs which then triggered the reinstall of create-strapi-app. I also have mongoDB installed locally.
Strapi has abandoned its support for NoSQL DBs. The MongoDB team might (if at all) write their own connector to MongoDB, however ETA is around July, and stable version ETA is around August.
SQLite is now the default DB. However I believe they recommend using PostgreSQL for production.
try with v3
npx create-strapi-app#3.6.8 fileName
Is running well with MongoDB
This worked for me guys,
Install strapi locally to your system using npm i strapi#alpha -g
Run mongodb locally on your system.
Use strapi new <project name> for creating a new project.
Choose your installation type as "custom"
This will avail "Mongo" on the list of supported Databases for Strapi.
Hope this will work for everyone.
Thanks
Reference:
https://strapi.gitee.io/documentation/3.0.0-alpha.x/guides/databases.html#mongodb-installation
Good day. I just finished upgrading my AWS RDS database engine from 9.6.22 to 10.17. I used these steps to make the upgrade using the AWS Console:
Create snapshot of target database to upgrade
Restore snapshot
Upgrade the restored snapshot's (which is now a new instance) DB Engine version.
After I did all of this, everything seems fine but when I access the database, this warning message appears
WARNING: psql major version 9.6, server major version 10.
Some psql features might not work.
I did not continue on my testing because I want to know what is the meaning of this first. Because I am fairly new in AWS as a whole. Thanks!
The meaning is that just because you are connecting to an upgraded database on some machine run by Amazon, the PostgreSQL installation on your local machine was not magically updated. psql from version 9.6 doesn't know what metadata tables were changed in v10, what features were removed and so on.
It would be a good idea to install a more recent version of PostgreSQL on your machine. By the way, upgrading to v10 was not the smartest move, as that version will go out of support in less than a year. You should upgrade to the latest version that your service provider offers.
The client program psql you are using to connect to the database is from an older version than the database it is connecting to. Some of the introspection features might not work. For example, psql from 9.6 won't know how to do tab completion for commands that were added to the server after 9.6.
This is generally not a major problem for psql (unless the server wants to use SCRAM authentication), but for optimal experience it would be good to install a newer client. Other tools like pg_dimp might not with at all against a server newer than they are.
We have the following requirements. Could anyone suggest which PostgreSQL package to choose?
Server supporting multiple connections on the same port
Trigger
GUI to interact with the server
Features to support back up & restore database
Ability to connect to a remote postgreSQL server
We would require it for both Windows 7 & OS X El Capitan
UPDATE:
The below link contains multiple links to download PostgreSQL. As we can not download all of them & try out, require someone's help to point us to the right package with the above mentioned components/features
postgres
postgres
pgAdmin
pg_dump, pg_restore, psql
psql lets you specify database (including remote) to connect to
All above works both windows and osX
EnterpriseDb has free packages for postgres that include commonly used components like pgAdmin (a GUI). They have packages for both Windows and OS X but I would use homebrew instead for OS X. Homebrew is an OS X package manager. There's several tutorials for installing postgres via Homebrew. Here is one.
You would install pgAdmin separately.
Installing via Homebrew is a little more complex but gives you more flexibility and capability.
If you're just starting out with postgres, the EnterpriseDB packages will be easier.
I downloaded what I believe to be the latest copy of Dreamfactory for Windows from Bitnami bitnami-dreamfactory-1.8.2-0-windows-installer.exe. I would like to connect to an IBM DB2 remote database. In using the Admin Console I don't see an option in the SQL Vendor dropdown for IBM DB2. Did I miss a configuration step? If not, what do I need to do to configure IBM DB2 as a Remote SQL DB? I can't seem to find a reference in the documentation for how to do this.
Update
I just installed the Bitnami Ubuntu vmware appliance and it has a DB2 dropdown. Therefore, there is a flaw in the Windows 1.8.2 self installer.
With a quick test of the windows installer, we did confirm the DB2 value is in the dropdown menu. Please try to refresh the window frame or clear browser cache to see if that helps.
Also, the Bitnami package released for 1.8.2 currently doesn't have the db2 driver installed by default. We are working on getting another build that has better default setup. In the mean time, this link has the Windows instructions. I will try to get a more detailed instruction set for Windows.
I am having Oracle 10g installed on my laptop and have downloaded ojdbc14.jar driver for the same. The problem is, my operating system is Windows 7, and I'm not having option to create a Data Source for Oracle since I m not having oracles driver installed. I m having option to create a Data Source for SQL server 6, but I want to get connected to Oracle. Please Help.
By 'Data Sources', I'm guessing that you mean Data Sources (ODBC), under Control Panel > Administrative Tools. Is this correct?
I've set up ODBC Data Sources that connect to Oracle databases before, but to do that I've needed the Oracle client to be installed. However, if you're having the full database installed on your laptop (as your question suggests), you won't need the client - that's only used to connect to databases running on other machines. I believe the full database contains everything in the client, so you should be able to set up an ODBC Data Source pointing to the database on your laptop once the database has been installed.
The ojdbc14.jar just contains the JDBC classes to talk to an Oracle database, and only programs written in Java (and other languages that run on the JVM such as Scala, Groovy or Clojure) can use it. This jar on its own not enough to be able to set up an ODBC data source.
Oracle currently has 1 version that is certified for windows 7. That version is 11.2. They have indicated that they plan to certify 10.2.0.5 if this happens there will likely be a patch that will be needed.
This is probably why the Data Source does not work, either ODBC or OLEDB.
Another possibility is that you have installed the 32bit version of Oracle and your OS is 64bit then you would need to use the 32bit Data Source administrative tools.
I have figured out the solution for my problem. All that I needed to do is put ojdbc14.jar file in my class path and then I was able to use it. Though by doing so, I needed to make some change in the code. I was no more able to use Class.forName("sun.jdbc.odbc.JdbcOdbcDriver") instead I needed to use Class.forName("oracle.jdbc.OracleDriver") also instead of using my data source as "jdbc:odbc:somename" I needed to use jdbc:oracle:thin:#localhost:1521:xe.