Google Cloud SQL: unsupported XML feature - google-cloud-platform

Do Postgres databases on Google Cloud SQL support an XML type field? I am trying to import a Postgres 9.5 dump which has XML type fields and it throws an error saying unsupported XML feature.
Full error message from Google Cloud SQL console:
ERROR: unsupported XML feature DETAIL: This functionality requires the server to be built with libxml support. HINT: You need to rebuild PostgreSQL using --with-libxml.
I couldn't find any way to rebuild PostgreSQL on Google Cloud.

Supported flags for postgres Cloud SQL instances are listed here. There is an open public Feature Request for supporting this flag. I suggest you to add your use case there which would higher the possibility of implementation.

Related

Apache Calcite CSV Adapter - SQL Client

I am working on the development of a Connector interface with Elasticsearch (translate SQL to API DSL query syntax) .
I am starting with Apache Calcite CSV Adapter as a first step to test Calcite capabilities.
I followed the tutorial https://calcite.apache.org/docs/tutorial.html 
My question is how to use the JDBC connector (and which configuration) in a SQL client like Dbeaver or Squirrel... ?
Thanks
Edit:
This my configuration but it's not working
Error:
The DBeaver documentation describes how to add a new database driver. You can specify whatever parameters you need as well as provide a Calcite JAR file so the necessary code is available.
The class name should be org.apache.calcite.jdbc.Driver. The URL Template will be something like jdbc:calcite:model=path/to/model.json where you specify a path to a model.json file which contains the necessary model to create the connection.

Error Configuring WSO2 data analytics server

I'm currently experimenting/working on WSO2. What i'm trying to do is to have Data Analytics server configured. I started by following the below specified URL
https://docs.wso2.com/display/AM210/Configuring+APIM+Analytics#9d6747f5c0074928b18599abe472987d (Quick Steps)
After performing all the steps, i get the following issue on APIM cmd prompt
YES Its pretty evident from the error that no such table exists BUT that is exactly the issue i'm facing. What could really be the cause here?
Consider the following points:
I've not followed ALL the steps mentioned on
https://docs.wso2.com/display/DAS310/Getting+Started (BUT are they
required?)
In the installation prerequisites for DAS, JDBC-compliant Connector for Java is required which I've not yet installed (BUT its not mandatory at the same time)
Most of the QUICK STEPS for the configuration of DAS in the specified URL i.e. https://docs.wso2.com/display/AM210/Configuring+APIM+Analytics#9d6747f5c0074928b18599abe472987d where already in place and i only had to
Set Up JDK, ANT, Maven
enable the analytics section in the API-M_HOME/repository/conf/api-manager.xml
add log4j.rootLogger=, DAS_AGENT to API-M_HOME/repository/conf/log4j.properties
add snappy-java_1.1.1.7.jar to DAS_HOME\repository\components\lib
Yet the issue persists, Do let me know of what you think. Thank you
Since you are following quick start guide please extract the WSO2 API Manager and the WSO2 API-M Analytics distributions (zip files), to the same directory (preferably an empty directory).
Also, you need to generate some traffic to the published APIs in order to analytics server to create this table for the first time.

Which versions of django can I use with google cloud sql?

I would like to know which versions of django can I use with google cloud sql. I am currently trying 1.8 but I guess it is not supported.
Is there any documentation on supported version?
Thank you
So, after contacting google cloud support to be sure about the possibilities, I will answer my question:
You can use any version of Django in appengine, you can install it to a lib module and then add the file appengine_config.py with the lines:
from google.appengine.ext import vendor
vendor.add('lib')
If you want to use the django mysql backend you can do so and you can use Google Cloud SQL first OR second generation. I am currently using second generation. There is a free trial and good documentation > https://cloud.google.com/appengine/docs/python/cloud-sql/django

Deploy Django project on Google App Engine

I have developed one example project in django1.4 & python 2.7, I want to deploy it on google app engine,
but how to configure my project as per App Engine we didn't get.
We have a site running on google app engine, but it is including with all html,js.
How do we configure a database on google app engine to deploy our django project?
Possibly the best option is to use Django Non-Rel. It's the only way (that I know of) to use the Django ORM (the django database interface) on Google App Engine without using Google's costly cloud SQL service. To do this, you'll need to use a customized version of Django and import several more libraries. It's a small project to get it up and running, but it's worth the effort. More information can be found on this website:
http://django-nonrel.org/
Note, that even though django-nonrel allows you to use the Django database interface, it will not allow you to use certain SQL features, such as joins. If you need joins, then your best option would be to use Google App Engine + Google Cloud SQL. Documentation for that is here.
Regarding the comments:
Yes, it can run on windows, I run it on Windows.
Also, the site allbuttonspressed.com is old and out of date, use the
one above for information.

WSO2 Identity Server 3.2.3. Missing Ability to Add External User Stores

What happened to the ability to add an external user store with custom tables in WSO2 Identity Server 3.2.3?
We are evaluating use of this IS and it appears an older version had this capability and the latest version does not.
Am I missing a configuration setting or has this capability been completely removed? Or is this a build configuration option?
Not having this feature is a show-stopper.
it's done through the config files - there is (seemingly) no ui component. I was able to connect to an external sql server user store via jdbc by manipulating the user-mgt.xml and master-datasource.xml files. Although next step would be to define a logical schema definition to map the id fields. e.g. running the mssql.sql script in /dbscripts on my sql server db will create the needed structure.