Menu
▾
▴
postgres-xc-general
|
From: Paulo P. <pj...@ub...> - 2012-09-17 21:48:07
Attachments:
signature.asc
|
Dear all, I'm testing postgres-xc with an existing Java EE solution of mine and right now I'm facing the following issue when reading from an entity I've just persisted: org.postgresql.util.PSQLException: ERROR: RETURNING clause not yet supported Here's what I'm doing: 1) I have a JDBC Connection Pool configured in my application server pointing to one of my coordinators; 2) In my application, I'm using Hibernate (Java ORM implementation) to persist my dat-model; 3) I insert a new entity to my database; 4) I get the ID of the object, that usually is available after inserting the new entity (I don't force RETURNING clause, but I believe the ORM may be doing it or something similar, if any); 5) I get the aforementioned exception. Is this a known issue? Cheers, -- Paulo Pires Ubiwhere |
|
From: Paulo P. <pj...@ub...> - 2012-09-17 22:05:48
Attachments:
signature.asc
|
OK, I've tried this with plain PostgreSQL and it works. I've executed the query by hand and the ID of the user returns properly. In postgres-xc the RETURNING clause is not yet supported. Any idea on when could this get to postgres-xc or at least could anyone please explain why it has not been yet included (any technical issues?)? Cheers, PP On 9/17/12 10:47 PM, Paulo Pires wrote: > Dear all, > > I'm testing postgres-xc with an existing Java EE solution of mine and > right now I'm facing the following issue when reading from an entity > I've just persisted: > > org.postgresql.util.PSQLException: ERROR: RETURNING clause not yet supported > > Here's what I'm doing: > 1) I have a JDBC Connection Pool configured in my application server > pointing to one of my coordinators; > 2) In my application, I'm using Hibernate (Java ORM implementation) to > persist my dat-model; > 3) I insert a new entity to my database; > 4) I get the ID of the object, that usually is available after inserting > the new entity (I don't force RETURNING clause, but I believe the ORM > may be doing it or something similar, if any); > 5) I get the aforementioned exception. > > Is this a known issue? > > Cheers, > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > -- Paulo Pires Ubiwhere |
|
From: Ashutosh B. <ash...@en...> - 2012-09-17 22:40:27
|
On Tue, Sep 18, 2012 at 2:05 AM, Paulo Pires <pj...@ub...> wrote: > OK, I've tried this with plain PostgreSQL and it works. I've executed > the query by hand and the ID of the user returns properly. > In postgres-xc the RETURNING clause is not yet supported. > > Any idea on when could this get to postgres-xc or at least could anyone > please explain why it has not been yet included (any technical issues?)? > > The RETURNING clause support will be available in the next release of XC. We are working on it. > Cheers, > PP > > On 9/17/12 10:47 PM, Paulo Pires wrote: > > Dear all, > > > > I'm testing postgres-xc with an existing Java EE solution of mine and > > right now I'm facing the following issue when reading from an entity > > I've just persisted: > > > > org.postgresql.util.PSQLException: ERROR: RETURNING clause not yet > supported > > > > Here's what I'm doing: > > 1) I have a JDBC Connection Pool configured in my application server > > pointing to one of my coordinators; > > 2) In my application, I'm using Hibernate (Java ORM implementation) to > > persist my dat-model; > > 3) I insert a new entity to my database; > > 4) I get the ID of the object, that usually is available after inserting > > the new entity (I don't force RETURNING clause, but I believe the ORM > > may be doing it or something similar, if any); > > 5) I get the aforementioned exception. > > > > Is this a known issue? > > > > Cheers, > > > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > > > > > _______________________________________________ > > Postgres-xc-general mailing list > > Pos...@li... > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > > -- > Paulo Pires > Ubiwhere > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Enterprise Postgres Company |
|
From: Michael P. <mic...@gm...> - 2012-09-17 23:43:09
|
On Tue, Sep 18, 2012 at 7:40 AM, Ashutosh Bapat < ash...@en...> wrote: > > > On Tue, Sep 18, 2012 at 2:05 AM, Paulo Pires <pj...@ub...> wrote: > >> OK, I've tried this with plain PostgreSQL and it works. I've executed >> the query by hand and the ID of the user returns properly. >> In postgres-xc the RETURNING clause is not yet supported. >> >> Any idea on when could this get to postgres-xc or at least could anyone >> please explain why it has not been yet included (any technical issues?)? >> >> > The RETURNING clause support will be available in the next release of XC. > We are working on it. > The patch for support of RETURNING will be committed in something like 2 weeks on the current development branch, so you may also consider testing your application not on a stable release but on Postgres-XC master branch. -- Michael Paquier http://michael.otacoo.com |
|
From: Paulo P. <pj...@ub...> - 2012-09-18 08:11:41
|
On 18/09/12 00:43, Michael Paquier wrote: > > > On Tue, Sep 18, 2012 at 7:40 AM, Ashutosh Bapat > <ash...@en... > <mailto:ash...@en...>> wrote: > > > > On Tue, Sep 18, 2012 at 2:05 AM, Paulo Pires <pj...@ub... > <mailto:pj...@ub...>> wrote: > > OK, I've tried this with plain PostgreSQL and it works. I've > executed > the query by hand and the ID of the user returns properly. > In postgres-xc the RETURNING clause is not yet supported. > > Any idea on when could this get to postgres-xc or at least > could anyone > please explain why it has not been yet included (any technical > issues?)? > > > The RETURNING clause support will be available in the next release > of XC. We are working on it. > > The patch for support of RETURNING will be committed in something like > 2 weeks on the current development branch, so you may also consider > testing your application not on a stable release but on Postgres-XC > master branch. Count me in for testing. Btw, when is the new release expected to happen? Is it still May 2013? > -- > Michael Paquier > http://michael.otacoo.com -- Paulo Pires |
|
From: Michael P. <mic...@gm...> - 2012-09-18 08:19:46
|
On Tue, Sep 18, 2012 at 5:11 PM, Paulo Pires <pj...@ub...> wrote: > > On 18/09/12 00:43, Michael Paquier wrote: > > > > On Tue, Sep 18, 2012 at 7:40 AM, Ashutosh Bapat < > ash...@en...> wrote: > >> >> >> On Tue, Sep 18, 2012 at 2:05 AM, Paulo Pires <pj...@ub...>wrote: >> >>> OK, I've tried this with plain PostgreSQL and it works. I've executed >>> the query by hand and the ID of the user returns properly. >>> In postgres-xc the RETURNING clause is not yet supported. >>> >>> Any idea on when could this get to postgres-xc or at least could anyone >>> please explain why it has not been yet included (any technical issues?)? >>> >>> >> The RETURNING clause support will be available in the next release of XC. >> We are working on it. >> > The patch for support of RETURNING will be committed in something like 2 > weeks on the current development branch, so you may also consider testing > your application not on a stable release but on Postgres-XC master branch. > > Count me in for testing. Btw, when is the new release expected to happen? > Is it still May 2013? > Yes, the next stable release is planned for this period. Might be a bit earlier or a bit later. A beta phase will be done before that though. -- Michael Paquier http://michael.otacoo.com |
|
From: Michael P. <mic...@gm...> - 2012-10-02 23:25:16
|
On Wed, Oct 3, 2012 at 2:27 AM, Paulo Pires <pj...@ub...> wrote: > > > On Tue Sep 18 11:21:21 2012, Michael Paquier wrote: > > > > > > On Tue, Sep 18, 2012 at 5:43 PM, Paulo Pires <pj...@ub... > > <mailto:pj...@ub...>> wrote: > > > > Hi Michael, > > > > Thanks so much for your support. > > > > Could you tell me if I should follow postgres-xc-developers@ or > > postgres-xc-committers in order to be notified as soon as > > RETURNING support is implemented? > > > > Sure. > > - The mailing list developper is used for conversations about features > > and patches, so you will be notified about the commit in GIT with that. > > - The commit mailing list is a mailing list where an email is sent > > automatically where there is a commit in GIT. So you should follow it. > > > > You can also follow this twitter bot: https://twitter.com/PostgresXCBot. > > This bot sends a tweet automatically when a commit is made with the > > header of the commit. > > You can also see the list of commits on Github: > > https://github.com/postgres-xc/postgres-xc/commits/master > > Last updates are from Sep 16th, so I think you don't make any "beta" > available. Am I wrong? > Well, I am working on the implementation of triggers, which is not that straightforward. So it requires time. The next beta of XC is planned for March or April. > > > > > I also don't mind dropping an email on the thread where you discussed > > about RETURNING on general mailing list once the stuff is committed. > > That would be awesome. I'm really needing this to continue my tests. > Regarding RETURNING, Abbas is working on that. He just needs more time to stabilize his patch as he is cleaning a lot of things, including things planner for remote query generation. -- Michael Paquier http://michael.otacoo.com |
|
From: Paulo P. <pj...@ub...> - 2012-10-24 09:33:06
|
On 03/10/12 00:25, Michael Paquier wrote: > > > On Wed, Oct 3, 2012 at 2:27 AM, Paulo Pires <pj...@ub... > <mailto:pj...@ub...>> wrote: > > > > On Tue Sep 18 11:21:21 2012, Michael Paquier wrote: > > > > > > On Tue, Sep 18, 2012 at 5:43 PM, Paulo Pires > <pj...@ub... <mailto:pj...@ub...> > > <mailto:pj...@ub... <mailto:pj...@ub...>>> wrote: > > > > Hi Michael, > > > > Thanks so much for your support. > > > > Could you tell me if I should follow postgres-xc-developers@ or > > postgres-xc-committers in order to be notified as soon as > > RETURNING support is implemented? > > > > Sure. > > - The mailing list developper is used for conversations about > features > > and patches, so you will be notified about the commit in GIT > with that. > > - The commit mailing list is a mailing list where an email is sent > > automatically where there is a commit in GIT. So you should > follow it. > > > > You can also follow this twitter bot: > https://twitter.com/PostgresXCBot. > > This bot sends a tweet automatically when a commit is made with the > > header of the commit. > > You can also see the list of commits on Github: > > https://github.com/postgres-xc/postgres-xc/commits/master > > Last updates are from Sep 16th, so I think you don't make any "beta" > available. Am I wrong? > > Well, I am working on the implementation of triggers, which is not > that straightforward. > So it requires time. The next beta of XC is planned for March or April. > > > > > > > I also don't mind dropping an email on the thread where you > discussed > > about RETURNING on general mailing list once the stuff is committed. > > That would be awesome. I'm really needing this to continue my tests. > > Regarding RETURNING, Abbas is working on that. > He just needs more time to stabilize his patch as he is cleaning a lot > of things, including things planner for remote query generation. Is this landing on master? I have been unable to find other development branches and even Abbas. I can only see you and Ashutosh as committers. > -- > Michael Paquier > http://michael.otacoo.com -- Paulo Pires |
|
From: Michael P. <mic...@gm...> - 2012-10-24 11:03:55
|
On Wed, Oct 24, 2012 at 6:14 PM, Paulo Pires <pj...@ub...> wrote: > > On 03/10/12 00:25, Michael Paquier wrote: > > > > On Wed, Oct 3, 2012 at 2:27 AM, Paulo Pires <pj...@ub...> wrote: > >> >> >> On Tue Sep 18 11:21:21 2012, Michael Paquier wrote: >> > >> > >> > On Tue, Sep 18, 2012 at 5:43 PM, Paulo Pires <pj...@ub... >> > <mailto:pj...@ub...>> wrote: >> > >> > Hi Michael, >> > >> > Thanks so much for your support. >> > >> > Could you tell me if I should follow postgres-xc-developers@ or >> > postgres-xc-committers in order to be notified as soon as >> > RETURNING support is implemented? >> > >> > Sure. >> > - The mailing list developper is used for conversations about features >> > and patches, so you will be notified about the commit in GIT with that. >> > - The commit mailing list is a mailing list where an email is sent >> > automatically where there is a commit in GIT. So you should follow it. >> > >> > You can also follow this twitter bot: https://twitter.com/PostgresXCBot >> . >> > This bot sends a tweet automatically when a commit is made with the >> > header of the commit. >> > You can also see the list of commits on Github: >> > https://github.com/postgres-xc/postgres-xc/commits/master >> >> Last updates are from Sep 16th, so I think you don't make any "beta" >> available. Am I wrong? >> > Well, I am working on the implementation of triggers, which is not that > straightforward. > So it requires time. The next beta of XC is planned for March or April. > > >> >> > >> > I also don't mind dropping an email on the thread where you discussed >> > about RETURNING on general mailing list once the stuff is committed. >> >> That would be awesome. I'm really needing this to continue my tests. >> > Regarding RETURNING, Abbas is working on that. > He just needs more time to stabilize his patch as he is cleaning a lot of > things, including things planner for remote query generation. > > Is this landing on master? I have been unable to find other development > branches and even Abbas. I can only see you and Ashutosh as committers. > Yes this is planned for master. He is working on it and there will be more stuff soon. Abbas is also a committer, just that he is not really committing a lot of things these days. -- Michael Paquier http://michael.otacoo.com |
|
From: Abbas B. <abb...@en...> - 2012-10-24 11:04:56
|
On Wed, Oct 24, 2012 at 2:14 PM, Paulo Pires <pj...@ub...> wrote: > > On 03/10/12 00:25, Michael Paquier wrote: > > > > On Wed, Oct 3, 2012 at 2:27 AM, Paulo Pires <pj...@ub...> wrote: > >> >> >> On Tue Sep 18 11:21:21 2012, Michael Paquier wrote: >> > >> > >> > On Tue, Sep 18, 2012 at 5:43 PM, Paulo Pires <pj...@ub... >> > <mailto:pj...@ub...>> wrote: >> > >> > Hi Michael, >> > >> > Thanks so much for your support. >> > >> > Could you tell me if I should follow postgres-xc-developers@ or >> > postgres-xc-committers in order to be notified as soon as >> > RETURNING support is implemented? >> > >> > Sure. >> > - The mailing list developper is used for conversations about features >> > and patches, so you will be notified about the commit in GIT with that. >> > - The commit mailing list is a mailing list where an email is sent >> > automatically where there is a commit in GIT. So you should follow it. >> > >> > You can also follow this twitter bot: https://twitter.com/PostgresXCBot >> . >> > This bot sends a tweet automatically when a commit is made with the >> > header of the commit. >> > You can also see the list of commits on Github: >> > https://github.com/postgres-xc/postgres-xc/commits/master >> >> Last updates are from Sep 16th, so I think you don't make any "beta" >> available. Am I wrong? >> > Well, I am working on the implementation of triggers, which is not that > straightforward. > So it requires time. The next beta of XC is planned for March or April. > > >> >> > >> > I also don't mind dropping an email on the thread where you discussed >> > about RETURNING on general mailing list once the stuff is committed. >> >> That would be awesome. I'm really needing this to continue my tests. >> > Regarding RETURNING, Abbas is working on that. > He just needs more time to stabilize his patch as he is cleaning a lot of > things, including things planner for remote query generation. > > Is this landing on master? I have been unable to find other development > branches and even Abbas. I can only see you and Ashutosh as committers. > Yes it will land on the master, there are no other dev branches. > > > -- > Michael Paquier > http://michael.otacoo.com > > > -- > Paulo Pires > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > -- -- Abbas Architect EnterpriseDB Corporation The Enterprise PostgreSQL Company Phone: 92-334-5100153 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. |
Thanks for helping keep SourceForge clean.
X