RE: Trafodion Client Binaries Download

It has to be built on Windows, and then put in the core/conn/clients directory to be picked up in the build packaging. --Steve *From:* Gunnar Tapper [mailto:tapper.gun...@gmail.com] *Sent:* Wednesday, March 16, 2016 3:49 PM *To:* user@trafodion.incubator.apache.org *Subject:* Re: Trafodion

RE: Upsert semantics

Fyi, JIRA-1843 “Allow USER option(s) to be defined as defaults in a table column definition” Exists to allow CURRENT_USER, SESSION_USER, and USER to be defaults. Roberta *From:* Selva Govindarajan [mailto:selva.govindara...@esgyn.com] *Sent:* Friday, March 18, 2016 1:10 PM *To:*

How to implement a TO_DATE UDF in Trafodion

Hi, all, I just learned the support of TO_DATE will be avialbe in Trafodion in R2.0 from Anoop, that is great! At present, due to the urgent requirement of current migration project, we cannot wait, so I want to write a UDF to do the TO_DATE. When I try to write it, I found it seems the UDF can

RE: Upsert semantics

I am sorry it was an honest mistake. I meant to sign and didn’t mean to send the message on behalf of Hans. Currently Trafodion engine doesn’t do the Qifan’s suggestion of evaluating the default expression and omit it from storage. However, I believe it is feasible only when Trafodion engine

Re: DCS default port

OK. I'll update the manuals accodingly. On Thu, Mar 17, 2016 at 12:04 AM, Anuradha Hegde wrote: > No.. It should be 23400. > > > > *From:* Gunnar Tapper [mailto:tapper.gun...@gmail.com] > *Sent:* Wednesday, March 16, 2016 10:42 PM > *To:*

Trafodion support of TO_DATE

Hi, all, I know there will be a new feature to support TO_DATE, currently, without this feature, is there any way to migrate a query using TO_DATE? Example: insert into myTbl (staff_id, orbat_code,operate_time,ip_arr,browser_version,orbat_desc)

Re: DCS default port

Is 37800 valid in 1.3.0? On Wed, Mar 16, 2016 at 9:36 PM, Venkat Muthuswamy < venkat.muthusw...@esgyn.com> wrote: > 23400 is the default port. (37800 is an old value). > > > > *From:* Gunnar Tapper [mailto:tapper.gun...@gmail.com] > *Sent:* Wednesday, March 16, 2016 8:35 PM > *To:*

RE: Trafodion support of TO_DATE

You will have to convert the TO_DATE part of the query to an explicit datetime literal that looks like: timestamp '2016-03-17 11:47:06' With TO_DATE support (this is on trafodion now but will be externally available as part of Traf 2.0), you can use the statement that you have listed.

Re: Upsert semantics

I agree omitting default values from storage is an optimization and as such it should provide the same UPSERT semantics as with other storage formats/optimizations. Specially our code could insert default value checking expression to verify that an value is exact the same as the default value

RE: DCS default port

No.. It should be 23400. *From:* Gunnar Tapper [mailto:tapper.gun...@gmail.com] *Sent:* Wednesday, March 16, 2016 10:42 PM *To:* user@trafodion.incubator.apache.org *Subject:* Re: DCS default port Is 37800 valid in 1.3.0? On Wed, Mar 16, 2016 at 9:36 PM, Venkat Muthuswamy <

Re: Trafodion Client Binaries Download

Hi, I'm adding [Binary is included in this release] to the manual. I need a bit of guidance on this: I noticed that the make package debug build creates a winodbc directory but that does not contain an installer? I also tried to build a release package but the resulting tar files don't contain

答复: Trafodion support of TO_DATE

Thanks Anoop, I see how to change it now. This will be some work to replace all literal in the application, so the coming TO_DATE feature of Trafodion 2.0 will be a great help for database migration project. Thanks, Ming 发件人: Anoop Sharma [mailto:anoop.sha...@esgyn.com] 发送时间: 2016年3月17日 12:05

Re: Trafodion Client Binaries Download

Are there any instructions for how to build it on Windows? I don't think we need it in the release package if we're instructing users on how to build it on Windows. Gunnar On Wed, Mar 16, 2016 at 5:00 PM, Steve Varnau wrote: > It has to be built on Windows, and then

RE: Upsert semantics

Here is what I found with phoenix, just to compare with phoenix’s behavior for upsert. Phoenix expects the table to have a primary key. Upsert specification is Inserts if not present and updates otherwise the value in the table. The list of columns is optional and if not present, the values

RE: Upsert semantics

I wonder if the CQD TRAF_UPSERT_WITH_INSERT_DEFAULT_SEMANTICS should be set to “SYSTEM” by default. It can take ‘SYSTEM’, ‘ON’ or ‘OFF’. For aligned format – SYSTEM would be treated as ‘ON’ – User can override it with ‘OFF’ if he/she needs merge semantics. For non-aligned format – SYSTEM