vertica

Disclaimer: My DB knowledge comes mostly from Mysql so I might misunderstand some things in vertica... I would like to know if there exist a technique of inserting/updating values in vertica while enforcing unique constrains across multiple sessions. Let's assume I have a table: 'id', 'unique_field', 'some_filed' And there is a unique constraint on unique_field. My understanding is that in vertica one first needs to do an insert and then do ANALYZE_CONSTRAINTS to verify if the constraint was violated. In my specific case, I have multiple sessions preforming INSERTS to the same table and they

I have some data set in a pandas data frame that I wish to write to Vertica. I've already created my table using the vertica_python library. What is the best way to write my data frame to Vertica? Often when connecting to Vertica, you can use Postgresql as a stand-in since certain parts of Vertica were originally based on Postgresql. from sqlalchemy import create_engine engine = create_engine('postgresql://user:pass@host:5433/MYDB') df.to_sql('table_name', engine) If this doesn't work you could try out the vertica-sqlalchemy package. Also, depending on the SQL created (and if the ODBC driver

Suppose I have a simple table: CREATE TABLE user( id INT NOT NULL PRIMARY KEY, name VARCHAR(32) NOT NULL, ) Is there a way to alter this table so id will become AUTO_INCREMENT field? I tried the following with no luck: ALTER TABLE (no such syntax) Creating another table with auto increment ID, and copying the data from the original one (didn't work because of the error: Cannot insert into or update IDENTITY/AUTO_INCREMENT column "id") Thanks! I would try to just rank the rows, and use the sequence for future inserts. \set AUTOCOMMIT 'on' CREATE TABLE t1 ( val char(1) ); INSERT INTO t1 VALUES (

Hi I have configured the DSN settings for vertica in Ubuntu 10.10 32 bit version machine. The settings are all fine and I have cross checked them. Here is my odbc.ini file: [VerticaDSN] Description = VerticaDSN ODBC driver Driver = /opt/vertica/lib/libverticaodbc_unixodbc.so Servername = myservername Database = mydbname Port = 5433 UserName = myuname Password = ******* Locale = en_US Similarly I have a odbcinst.ini file. when I run the command: isql -v VerticaDSN I get the following error: [S1000][unixODBC][DSI] The error message NoSQLGetPrivateProfileString could not be found in the en-US

I'm trying to connect to a Vertica database using SQLAlchemy. I came across and installed a Vertica dialect at https://github.com/jamescasbon/vertica-sqlalchemy . I've also installed pyodbc. Using a basic tutorial at http://www.pythoncentral.io/sqlalchemy-orm-examples/ , I have the following code snippet :- from sqlalchemy import Column, DateTime, String, Integer, ForeignKey, func from sqlalchemy.orm import relationship, backref from sqlalchemy.ext.declarative import declarative_base from sqlalchemy import create_engine from sqlalchemy.orm import sessionmaker Base = declarative_base() class

Suppose you have columns ID | A | B | C 1 | 3 | 1 | 2 2 | 5 | 9 | 1 3 | 1 | 2 | 3 and you want the columns concatenated such that the end result would look like ID | ABC_value_DESC | ABC_value_DESC_colnames 1 | 3,2,1 | A,C,B 2 | 9,5,1 | B,A,C 3 | 3,2,1 | C,B,A where you want to get the col values in Descending order within the new column ABC_value_DESC and then return corresponding name of column in the new column ABC_value_DESC_colnames . How can you do the concatenation of values of multiple columns into a new column in Descending order and return column names by value order (not name order)

My fellows at work and I are trying to develop a web application using Laravel with a Vertica database. The only problem is that as soon as you use bindValue or bindParam with this specific database, PHP crashes with a segmentation fault. So I've written a PDO wrapper class that redirects calls to the PHP_ODBC module and that actually works. I was now wondering how to integrate it in Laravel if such a thing is even possible. Okay so after a lot of trial and error, my co-workers and I managed to get things up and running. The most time-consuming part turned out to build the wrapper. Assuming