Re: [JDBC] j2ee compatiable jdbc driver on jdbc.postgresql.org?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, I understand. So, why are people talking about support for JDBC3 where JDBC2 support isn't even there? On 26-Oct-2001 Barry Lind wrote: Ned, It may or may not work. That file hasn't been changed in a long time, so I doubt anyone is using it and therefore it may no longer work. I don't want to give people the false impression that the javax.sql set of extensions to JDBC2 is supported by the jdbc driver by providing a jdbc7.2-1.2ee.jar file when we only implement 1 interface out of the 13 defined in that package. thanks, --Barry Ned Wolpert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Humm... are you saying that the class PostgresqlDataSource doesn't work? I guess I'm not sure what doesn't work with the driver. (Course, I've been using PoolMan as the datasource to wrap the postgresql default connection rather than using the datasource object, so I haven't been testing this myself, yet.) On 26-Oct-2001 Barry Lind wrote: Ned, There really isn't a j2ee driver for postgres. If you build the j2ee driver it is essentially the same as the j2se driver. So I don't see any reason to confuse people by letting them think there really is a difference by having two different java2 drivers to choose from on the web site. The only difference is some code that I consider questionable, and I don't think even works. thanks, --Barry Ned Wolpert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks- I checked out the jdbc driver for 7.2b1 on the jdbc.postgresql.org website (http://jdbc.postgresql.org/download/jdbc7.2b1-1.2.jar) and I was going to submit it for testing with the castor project. One problem... it's only the default driver. I think the website should have the default one, and the j2ee (jdk1.2e+) one available. Thoughts? Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE72J4xiysnOdCML0URAvl6AJ90aNX33co+5BH23/kgeK2YX/OlvwCdHbMV voujwk16eZ04pJvH5iTCJTQ= =36ME -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED]) Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE72YusiysnOdCML0URApmaAJ9rHvs0TGF0FdgKTq+ZE86bi7o4jgCfYJ7a /QTFI0POE6TO6hQEBwidE3g= =YFMc -END PGP SIGNATURE- Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE72aI7iysnOdCML0URApAJAJ0eDaIF+I81WoA+NI2kBeD2vpCmRgCfZriP dcEU0c1UR2fZI3RTJkGddpw= =DQ7t -END PGP SIGNATURE- ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [JDBC] j2ee compatiable jdbc driver on jdbc.postgresql.org?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26-Oct-2001 Barry Lind wrote: This is a community of volunteers. So if someone wants to work on JDBC3 that is fine. We don't have the option of telling people how they should spend their time. My bad. I didn't mean to alienate. Sorry if I came off that way. Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE72bgRiysnOdCML0URAs3XAJ9iH9XCAl2sCGnEH75deA6dmtwHXQCcCFDk G1hiweqEK9YGKsiMsXNQtYA= =ZU7Y -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[JDBC] j2ee compatiable jdbc driver on jdbc.postgresql.org?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks- I checked out the jdbc driver for 7.2b1 on the jdbc.postgresql.org website (http://jdbc.postgresql.org/download/jdbc7.2b1-1.2.jar) and I was going to submit it for testing with the castor project. One problem... it's only the default driver. I think the website should have the default one, and the j2ee (jdk1.2e+) one available. Thoughts? Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE72J4xiysnOdCML0URAvl6AJ90aNX33co+5BH23/kgeK2YX/OlvwCdHbMV voujwk16eZ04pJvH5iTCJTQ= =36ME -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [JDBC] [PATCHES] Ant configuration
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Oct-2001 Peter Eisentraut wrote:
Gunnar Rønning writes:
| * In numerous attempts I have failed to convince Ant to place the built
| files in a tree different from the source tree. This really makes it a
| pain to build for multiple architectures (in Java, architecture =
| different jdk).
javac srcdir=${src}
destdir=${build}
classpath=xyz.jar
debug=on
/
Is that what you want ?
Yes, but ant refused to recognize the srcdir as absolute and thinks it's
relative to the build dir. (Or at least it was something stupid like
that; it's been a while.)
That should work fine. I've been doing that since Ant version 1.3. Do you have
a specific case that doesn't work? (You can always specify absolute paths in
the properties, if you like...)
From the Ant manual :
It is possible to use different compilers. This can be selected with
the build.compiler property.
Yeah, but how do you set the build.compiler property? This requires
pretty advanced knowledge.
You can either set-it in the build.xml file via a property tag
property name=build.compiler value=jikes/
or during the startup of ant using the -D flag. (set the ANT_OPTS var to
-Dbuild.compiler=jikes in your environment before running ant)
Virtually,
Ned Wolpert [EMAIL PROTECTED]
D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE71etAiysnOdCML0URAkk6AJ9Op2uOIfbd4UokyhsJqS1/S4ZgjQCeJZd4
vmRbTwuQadIuhyez/86OpF0=
=xk1y
-END PGP SIGNATURE-
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Re: [JDBC] FW: Re: [PATCHES] Ant configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23-Oct-2001 Jayesh K. Parayali wrote: Just a thought. Why not separate postgres and postgres jdbc in that case? To be honest, this is the one thing I want to avoid if possible. Its important that the postgres build system builds the 'official' interfaces as well, since it keeps the two connect tightly. I prefer to use ant to build Java code, but to be honest, I really just want to be able to type either of the following, in the src/interfaces/jdbc directory: ant jar or make jar Both should give the same results. (Its kinda silly that the current technique has 'make' call 'ant', but anyways...) The only two issues are multiple build tools and ease for building the jdbc driver for non-UNIX users. And to be more honest, I think we've spent too much time on this as is. If we can't decide as a group, we should either a) vote on it (Least the CVS committers should) or b) leave it for now. Either way, I'm going to stay out of this discussion for now. Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE71bdxiysnOdCML0URAoXlAJ4w6Nd9pXuCoJAawEpxBaE/DADsRwCfS0dK tjPvtMsIWudhz641Ro12SgE= =/uGM -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
OT Re: [JDBC] Ant installation (and other) issues!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21-Oct-2001 Peter Eisentraut wrote: Per-Olof Norén writes: The Ant build system is making its way to be a de facto standard for building java applications as it is built for the purpose. Make as been the standard for building any application for about 30 years. GNU-style configure has been the standard for configuration management for about 10 years. Windows NT and Visual Basic have been the standard for enterprise computing for 5 years. Thank you very much. ;-) And I thought Java was the standard for enterprise computering long before Visual Basic. :-) [Corba? What's Corba? CICS anyone?] I guess standards are what I use, and everyone else is violating them. ;-) [Sorry, couldn't resist...] Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE71Hn1iysnOdCML0URAtdAAJ9Zikvs/jCqqG6IG1I9ltdBukiIlACeJRtz QHCZWyBV04b/F7KabTA0Htc= =S1Xx -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [JDBC] Ant installation (and other) issues!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22-Oct-2001 Bruce Momjian wrote: A more important point is that we are not a java-only codebase. If we were, I could see a stronger argument for Ant. As it is now, we have to weigh using a Java-standard Ant vs. a PostgreSQL/C-standard makefile solution. Yes, which goes back to my original question. Would someone want to build the JDBC driver without building the rest of postgresql? If this is the case, then we need to make sure that we provide the tools needed build the JDBC driver in this type of environment. If this is not the case, then it doesn't/shouldn't matter, since the build is directly linked to postgresql. Let me ask people this question: Do we support building of the JDBC driver externally to building postgresql? Or, do we 'ship' or otherwise make available the various JDBC driver in pre-build jar/binaries? Up to this point, people have basically been expected to get the latest JDBC driver from CVS and re-build it. If this is expected to continue, I recomend making the JDBC driver easy to build outside of the postgresql project. However, if the releases will start to contain all the fixes from 7.2 and beyond, then it doesn't matter to non-postgresql developers as much. (It may still matter, but its less of a big deal.) (Personally, I love Ant as a development tool. But the quality of Ant isn't the issue here, its ease of development. Multiple build-tools can create confusion. If 'from now on', we don't expect individuals to build the JDBC driver on their own, but use binaries, than simplfying the build procedure by only using make should be fine.) Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE71KimiysnOdCML0URAmjZAJ9n4FjIXYrdN8rCvciEOSwag8QJZACfZhwO OYeJZf/BynzKO18trG5y9yM= =sDRr -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [JDBC] [PATCHES] Ant configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20-Oct-2001 Gunnar Rønning wrote: | * Ant doesn't provide an exit status; you have to watch the build to see | if it works. This is unacceptable. Hmm. Anybody with a solution here ? Actuall, it does. Example: [wolpert@wolpert configTest]$ ant build Buildfile: build.xml prepare: build: BUILD SUCCESSFUL Total time: 2 seconds [wolpert@wolpert configTest]$ echo $? 0 [wolpert@wolpert configTest]$ ant build Buildfile: build.xml prepare: build: [javac] Compiling 1 source file to /home/wolpert/test/configTest/classes [javac] /home/wolpert/test/configTest/src/GetAll.java:25: ';' expected [javac] jdo.setDatabaseName(configTest); [javac]^ [javac] /home/wolpert/test/configTest/src/GetAll.java:24: cannot resolve symbol [javac] symbol : class fds [javac] location: class GetAll [javac] jdo.setConfiguration(/database.xml);fds [javac] ^ [javac] /home/wolpert/test/configTest/src/GetAll.java:25: jdo is already defined in getDatabase() [javac] jdo.setDatabaseName(configTest); [javac] ^ [javac] 3 errors BUILD FAILED /home/wolpert/test/configTest/build.xml:35: Compile failed, messages should have been provided. Total time: 4 seconds [wolpert@wolpert configTest]$ echo $? 1 [wolpert@wolpert configTest]$ Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE71FvwiysnOdCML0URAqiRAJ4g8TL2aY9fAj25JzOw+mabnBG8PACggEOK xQOWn7giK++ZRDAsfyDtzsE= =M4Ld -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [JDBC] Whatever ... JDBC build patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20-Oct-2001 Peter Eisentraut wrote: How do distributors that need to build all driver types proceed ? I haven't seen one yet, but theoretically they should configure several different build trees from one source tree. Of course, this doesn't work with Ant, but it's trivial with GNU make. Actually, I think you can, if I understand the question. Simply have multiple targets in the build process, one per driver type. Each target builds the driver if and-only-if the needed classes are loaded. Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD4DBQE71Fx+iysnOdCML0URAvAJAJjcYuLk2CCeL1wooZ2dYTveYKxbAJ4xZ5z4 HzjKi22efx295LsmMfo5kw== =WdGU -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: FW: Re: [JDBC] [PATCHES] Ant configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19-Oct-2001 Bruce Momjian wrote: One significant issue here is that unlike our other binaries, the JAR files run on any platform so they don't really need to compile in MS Win. They can just download it from a web site or we could ship the jdbc JAR ourselves. True. I was really looking at it from those who wanted to build the jar from source. If we make the jarfile available from the website, that's good for the PostgreSQL releases, but it may not help those who want/need the JDBC driver updated from CVS. Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE70LuNiysnOdCML0URAn2tAJwOg8HpKskzyVvwucubAJ8/teXMgwCdENc1 Siu6Fx305Zh69RG5+U/Vbx4= =SXet -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
FW: Re: [JDBC] [PATCHES] Ant configuration
I meant to send this to the group... -FW: [EMAIL PROTECTED]- Date: Fri, 19 Oct 2001 10:45:43 -0700 (MST) Sender: [EMAIL PROTECTED] From: Ned Wolpert [EMAIL PROTECTED] To: Barry Lind [EMAIL PROTECTED] Subject: Re: [JDBC] [PATCHES] Ant configuration -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Two cents with of thought... :-) On 18-Oct-2001 Barry Lind wrote: * People with Java background probably know Ant better that 'make'. Ant seems to become 'build tool of choice' in Java world. Perhaps, but I'm not convinced that either of these arguments is true. I have seen make used by more projects than ant, and a developer building postgres from source, certainly needs to be familiar with make. Ant is great in a pure-java project. I have seen ant used as the primary build engine in many Java projects, and it works great for me. But, here are some (conflicting) thoughts. 1) To some degree, the make process of PostgreSQL should be consistant. Ant and Make are two seperate building systems. Its easier to put the JDBC driver into make than it is to put postgresql into ant. 2) Correct me if I'm wrong, but currently, Make is needed to run Ant in the JDBC driver anyways, right? (To grab the version numbers and set the properties when running ant) Yet... 3) Java is system independant, and the JDBC driver is a client piece. I should be able to compile the JDBC driver outside of PostgreSQL server if I wanted to, right? Example, I can't compile PostgreSQL on windozes 95. But I could compile the JDBC driver via ant if Java and ant are installed. (Or, rather, I should be able to) 4) Ant doesn't need to be 'installed' in other projects. Rather, they include the needed ant libs in the CVS, which is allowed by the license, and create a build script to call the ant process to build. (Usually a build.sh and a build.bat) We could do that to also set the version numbers rather than have make do it. I guess I can make an argument either way. The real way to answer this is to ask if one cares if you can build the JDBC driver on window's only platform without cygwin installed. -If the answer is no, that one wouldn't build the JDBC driver without building the rest of postgresql, then the build process should be tied to make, like the rest of postgresql, for simplisity in maintence. -However, if the JDBC driver should be able to be built without having to build postgresql, (on platforms without UNIX-compatiablity layer like cygwin) for client use only, then yes, use Ant to achive platform-independance. I'm lucky enough to only work with Linux, so I don't really care on the outcome of this :-) I can work with either. Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE70GbGiysnOdCML0URAnl5AJ9VkJs0QXr1GEzzFVxW5CzNLDRl1wCfbOmM O2tENKYPCsDAx6I42NoYh5U= =CSwI -END PGP SIGNATURE- --End of forwarded message- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [JDBC] [PATCHES] Ant configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19-Oct-2001 Barry Lind wrote: Did you send this just to me or the entire list. It appears that you sent it just to me. I think the good points you make here should be seen by everyone. Can you send it to the pgsql-jdbc list? Whoops. Yeah, I just now resent it to the group. Thanks for catching that. Specifically, if we can include the ANT libraries in our CVS then my objection to ANT (requiring users to trackdown and download ANT) goes away, and I would then suggest we continue to use ANT for the other reasons you mention. Works for me. As I mentioned in my last email, I'm easy about this one. As long as I can build it in Linux/UNIX, I'm happy. Its an added benefit to the postgresql community that it can be built on Windows and Mac. Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE70HePiysnOdCML0URAinrAJ9ejMSsr0TZm157jso5MSDAEKtMdwCfRCzy iIQ3byuD7zyFsM96QgoWsnA= =x5M1 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [JDBC] New backend functions? [was Re: JDBC changes for 7.2.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like your function name, get_last_returned_oid(). That works for me. On 23-Aug-2001 Tom Lane wrote: Ned Wolpert [EMAIL PROTECTED] writes: Should the backend support the function getLastInsertedOID() or even getLastInsertedPrimaryKey() (or both)? I don't think you have any chance of doing the latter --- for one thing, how are you going to declare that function's return type? But the former seems doable and reasonable to me: whenever an OID is returned to the client in an INSERT or UPDATE command result, also stash it in a static variable that can be picked up by this function. Please pick a more SQL-friendly (ie, case insensitive) naming convention, though. And note that it'd apply to both INSERT and UPDATE. Maybe get_last_returned_oid() ? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED]) Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7hWGbiysnOdCML0URAkqAAJ9Liv8VS+CPMYozG1q1tuy7vGLuEACfUJRM Hdbns8MxyOVgurx5ztV8YZU= =BbF3 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[JDBC] Re: JDBC changes for 7.2... some questions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually, it's not a new function on the server... I'm just trying to find a way to access the getInsertedOID() method in the statement object without having direct access to the statement object. (My use-case is when the JDBC driver is wrapped in a pooling manager, like PoolMan, it wraps all classes.) I wanted to catch the line 'select @@last_oid' which would return a result set with the single entry based on the results of the method call 'getInsertedOID' but some people didn't like the syntax. So, I'm seaking comments to see if there is a better syntax people like, as long as they don't mind the functionality. One option is the 'faking' of the function call on the server, which really isn't a good option in itself, but outside of my original 'catch' line, its all I got. What's your thoughts? Do you see the need for the functionality? Do you have a solution that I need? On 22-Aug-2001 Barry Lind wrote: I am assuming that this would be a new function in the server. Therefore this wouldn't be jdbc specific and would be available to all client interfaces. I don't see what this really has to do with JDBC. thanks, --Barry Ned Wolpert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, so you're not opposed to the idea then, just the syntax. Does anyone oppose having this concept in the JDBC driver? And what syntax is acceptable? Could we just do 'select getInsertedOID()' which would break people who have functions called getInsertedOID() of course... On 21-Aug-2001 Tom Lane wrote: Ned Wolpert [EMAIL PROTECTED] writes: What about the 'select @@last_oid' to make the getInsertedOID() call available even when the driver is wrapped by a pooling manager? How do people feel about this? Yech. At least, not with *that* syntax. @@ is a valid operator name in Postgres. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7gv5yiysnOdCML0URAq7qAJkBRhAcE9wctn7bUAv7UMwN3n9+nwCeJR4V ymYTw8l3f9WU4V5idFsibAE= =UQ2M -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED]) Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7g+agiysnOdCML0URAvbvAJ9GO/spmwQYZessjk4IenhtPuguSwCdHRQN xH+tnGqKpmg/UOSnxOevek0= =pcr+ -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [JDBC] Couple of patches for jdbc driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I guess my question is, when I submitted the patches after 7.1.2 was released, I was hoping they would be in the next release, 7.1.3 Is there a way for my patches to make it into the next release, which I assume is 7.2? Or, is the current source-tree geared for 7.2 all-along? On 21-Aug-2001 Tom Lane wrote: Ned Wolpert [EMAIL PROTECTED] writes: (You patched this about two months ago.) Specifically, the 1.11 version of jdbc2/PreparedStatment.java file has the patch, but the 7.1.3 released does not. How do we propragate patches into the main branch for releasing? At this point, we don't; it's quite unlikely that there will be a 7.1.4, considering that we hope to be in 7.2 beta within a month. As far as JDBC goes, lots of people seem to be using CVS snapshots quite happily, so I'm not sure an official back-patch is needed anyway. regards, tom lane Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7grT5iysnOdCML0URAjg3AJ9Zb45j8askvzCw4KeJes4Tx6zDSQCffcE7 HgvGPQt1/OnREkzSfG4AS90= =vUv3 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[JDBC] JDBC changes for 7.2... some questions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks- I'm looking into some modifications for the Castor project on how we get identies from inserted objects into the database. Specifically, if we have used the SERIAL type to link in a sequence number during row insertion, it would be great to get that sequence number when we do the insert. Both Oracle and mssql have something to provide this. Getting the OID would be second-best solution for us. Now, I understand that in the Statement class, we have getInsertedOID() in the table. However, the problem we run into is that this isn't accessiable if we use something like poolman to provide database pooling of connections. (You get the poolMan Statement object which is wraps the Statement classes of the driver.) So, what I'm looking for is some of the following ways to get the primary key back, or the OID if nothing else... 1) Being able to use the RETURNING clause in prepared statements, like this INSERT INTO tableName (key1,...) VALUES (value1,...) RETURNING primKeyName INTO ? Which is what Oracle provides. 2) Working like Sybase and call select @@OID on the next call, which would be trapped by the statment object to return a resultset with the oid of the last inserted oid. 3) or, someother way that where one doesn't need direct access to method calls to get 'getInsertedOID()', but indirect ones. Thoughts? Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7gr83iysnOdCML0URAj+QAJ91RZXOoEA+xnu68YhIA4euNfIWOgCfcG1/ 5L5ATkdL/wPwTnbQy0NI2jI= =l/7B -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [JDBC] JDBC changes for 7.2... some questions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What about the 'select @@last_oid' to make the getInsertedOID() call available even when the driver is wrapped by a pooling manager? How do people feel about this? (I would be happy to contribute to the codebase for this one.) I understand the RETURNING clause is more work... and I would like to help out on that for 7.3. On 21-Aug-2001 Tom Lane wrote: Ned Wolpert [EMAIL PROTECTED] writes: 1) Being able to use the RETURNING clause in prepared statements, like this INSERT INTO tableName (key1,...) VALUES (value1,...) RETURNING primKeyName INTO ? Which is what Oracle provides. INSERT ... RETURNING was discussed recently, and I think people agreed it's a good idea, but it got hung up on some unresolved issues about how it should interact with ON INSERT rules for views. Search the pghackers mailing list archives for details. At this point I think it's probably too late to consider it for 7.2, but I'm still open to doing it in 7.3 if we can come up with a bulletproof spec. regards, tom lane Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7gtIoiysnOdCML0URAmgIAJwJVf2BGhFq88bXHY3yni9qzGohegCdHmPf 7Xnb57gfiP2xoMC8x5mIhWU= =p5Bx -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [JDBC] JDBC changes for 7.2... some questions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it should interact with ON INSERT rules for views. Search the pghackers mailing list archives for details. At this point I think it's probably Ugh... a quick search shows me asking this same thing in May, when the 'big TODO' list was being commented on. Now that I remember, I thought that the RETURNING clause was being implemented. I didn't realize there wasn't agreement on it. I need to pay more attention to what I write. :-) Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7gtSBiysnOdCML0URAtXNAJ4+W3AgpEk5QZM5IKCFFMQ2tGP5UQCeM1Lx TXQw4pL4ew65B1iH+EfmZhk= =Ho0k -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [JDBC] JDBC changes for 7.2... some questions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, so you're not opposed to the idea then, just the syntax. Does anyone oppose having this concept in the JDBC driver? And what syntax is acceptable? Could we just do 'select getInsertedOID()' which would break people who have functions called getInsertedOID() of course... On 21-Aug-2001 Tom Lane wrote: Ned Wolpert [EMAIL PROTECTED] writes: What about the 'select @@last_oid' to make the getInsertedOID() call available even when the driver is wrapped by a pooling manager? How do people feel about this? Yech. At least, not with *that* syntax. @@ is a valid operator name in Postgres. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7gv5yiysnOdCML0URAq7qAJkBRhAcE9wctn7bUAv7UMwN3n9+nwCeJR4V ymYTw8l3f9WU4V5idFsibAE= =UQ2M -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [JDBC] Bug-report (was: JDBC driver in pgsql 7.1 build problem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Date: Fri, 4 May 2001 19:26:48 +0200 From: Marko Kreen [EMAIL PROTECTED] Has anybody had success compiling unpatched 7.1 JDBC driver with JDK1.3 and Ant 1.2/1.3? If not, could this patch be applied? Ant 1.4 betas seem to be ok. Yes. I could compile 7.1 with ant 1.3 without a problem. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Public key at http://www.keyserver.net iD8DBQE68vCUiysnOdCML0URAhaFAJwPk4muzSP6c5b+HCfZL/3N+KBv/ACdGke9 eFvhpOC1sWEeXmw9ozLfCR8= =rg36 -END PGP SIGNATURE- -- Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [JDBC] Returning oid or primary key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 From: Bruce Momjian [EMAIL PROTECTED] Date: Thu, 3 May 2001 13:42:23 -0400 (EDT) Certainly the portable solution is to get RETURNING into the backend so you can decide what you want to return. I agree. Is that currently planned for the next release? -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Public key at http://www.keyserver.net iD8DBQE68ZjfiysnOdCML0URAnAkAJ4h2r21+uvdZzw14Prmy8SgvqJs2QCeMMN8 YpwRmYJkfJdzZnkpqTLfI3Q= =PqCG -END PGP SIGNATURE- -- Virtually, Ned Wolpert [EMAIL PROTECTED] D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [JDBC] JDBC Pooling driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Don't mean to reply to my own message... but... Just an additional thought. Instead of creating a new pooling technique in PostgreSQL jdbc driver, could we do a specialized select that would return the 'getInsertedOid()' instead? (Select $_gett_inserted_oid) Does that make sense to others? (Kinda like what oracle's and other jdbc driver do.) Date: Mon, 30 Apr 2001 14:00:32 -0400 (EDT) From: Ned Wolpert [EMAIL PROTECTED] Folks- Got a question about using the PostgreSQL JDBC driver with pooling. Using 7.1, I noticed the extra functionality with the JDBC driver, like getInsertedOid(). I love it, since it helps with sequence numbers an integration with Castor. However, since the PostgreSQL JDBC driver doesn't have pooling connections as an option, I use PoolMan (or other) to pool connections. When I do this, I no longer have access to these PostgreSQL specific features. Is there any plans for adding this functionality into the JDBC driver? Is this something that others are looking for? -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Public key at http://www.keyserver.net iD8DBQE67cjuiysnOdCML0URAmWgAJ46xLa1Qt3g38JatXfPhfZ4kdDvxwCfeu3b i41kITdbIWdkLXk/8ldZ5Vg= =/S4b -END PGP SIGNATURE- ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
