Hi Noam, The Phoenix JDBC driver is an embedded driver, so I wouldn't recommend using a connection pool. The underlying HConnection to the cluster is shared among all connections for the same client JVM, so creating new connection has almost zero overhead (we're just instantiating a few instances).
If you don't want to create your own DUAL table, you can always use the SYSTEM.CATALOG table (with a LIMIT 1 clause). Thanks, James On Thu, Nov 27, 2014 at 11:07 AM, <[email protected]> wrote: > You can always create a table with one column in it and just insert one row. > > > > And you can use as dual table all day long. > > > > Thanks > > Deepak Gattala > > > > From: Bulvik, Noam [mailto:[email protected]] > Sent: Thursday, November 27, 2014 1:05 PM > To: [email protected] > Subject: is there something like dual table in phoenix > > > > HI, > > We are using connection pool and there is a need to have a general SQL to > test if connection is stil open. > > In Oracle there is something like select * from dual; > > In Impala you can use select 1 without table name > > > > What can be used for phenix ? both are not valid > > > > Regards, > > Noam > > Information in this e-mail and its attachments is confidential and > privileged under the TEOCO confidentiality terms that can be reviewed here.
