I have a table in a SAP HANA database which contains currency codes and their symbols, but when I try to read them in my PHP program via ODBC the rows containing symbols are not returned in the result set.
Test script:---------------CREATE TA...
I have two tables called PRODUCT and PRODUCT_REVISION which are constructed as follows:
CREATE TABLE product (
product_id nvarchar(40) NOT NULL,
product_name nvarchar(80) NOT NULL,
PRIMARY KEY (product_id)
);
CREATE TABLE product_revision (
...
I have just installed Sap HANA Express Edition in a virtual machine on my Windows 10 PC and am trying to use HANA Cockpit to manage the databases I wish to use in my application. However, when I open up Cockpit in my browser I do not see any way to o...
I have installed HANA Express Edition on a Windows 10 PC which I am accessing via a PHP application. I have created several tables in several database, but when I insert data with text in lower case it is being returned in uppercase when I read it ba...
I have installed SAP Hana Express Edition (virtual machine method) on my Windows PC so that I can use it with my PHP application. I have created a couple of databases and loaded data into several tables, and I can access these OK with my PHP applicat...
I am using the odbc_exec() function. I do not use PDO or prepared statements. The query that is being executed looks like the following:UPDATE unit_of_measure SET `uom_symbol`='€' WHERE uom_id='EUR';where uom_symbol is defined as NVARCHAR(4).The sa...
It is not the identifier which is uppercased, it is the value for that identifier. In order to force all searches on text fields to be case insensitive I am using SET SESSION 'CASE_SENSITIVE'='FALSE' on each connection. Unfortunately I have discovere...
I could not find that page very easily as it is buried deep in the documentation. I tried doing a search on 'UTF8' but got nothing. A poster in another newsgroup advised using the Windows ODBC Data Source Administrator to put 'CHAR_AS_UTF8=TRUE' in t...
This is not documented anywhere. I found a post on stackoverflow which said I should put CHAR_AS_UTF8=TRUE in the additional connection properties of the ODBC Data Source Administrator, but this didn't make a difference. I have tried your suggestion ...
