|Subject||RE: [IB-Architect] Re: New API -- Request for Comments|
|Author||Claudio Valderrama C.|
> -----Original Message-----[Connections v/s txns]
> From: Jim Starkey [mailto:jas@...]
> Sent: Jueves 1 de Junio de 2000 9:48
> You would need two Connection objects. If the second were created byAh, it's a limitation from the pov of the interface. If you do that
> Connection::clone(), there would be only one database attachment. In
> my implementation, there are no limits.
optimization internally with clone(), then I do not have more observations.
> Properties (abstract replacement for Parameters) is used only to passAn important point I missed in the first review. Then better as they are.
> an arbitrary and open ended set of named values on the openDatabase
> and createDatabase calls, and is not really part of the object model.
> Your point about making the method names parallel to PreparedStatementThanks. While less names I have to remember, easier is the life.
> is well taken. I chose to use "put" rather than "set" since there can
> be multiple values.
> >- As I see things, the only way to set Parameters' values isWell, if Parameters have one only function and meaning as SQL tokens, then
> through strings
> >in the putValue functions, is this the ODBC way? Is this practical?
> Yes, but I think this is appropriate for the extremely limited use
> of Parameters/Properties.
> >- Why do all PreparedStatement.setXXX functions take an index?This is the common level denominator, I guess, because the engines seem to
> Probably it's
> >fast, by a field name would be clearer in several cases.
> The PreparedStatement::setXXX guys are used to set values for parameter
> markers ("?"), which don't have names.
use all of them the "?" to mark parameters. However, I'm trying to simplify
the case of the same parameter appearing more than one time, a simple
setting by name could help life a bit. One starts to get used to high level
components hat use names... even if the "?" is the symbol used internally by
> >- What's ResultList and how is it used?Maybe an UDF?
> Output of a full text search. InterBase doesn't support it.
> I've had trouble with MSVC++ throwing localing object instances thatI've had trouble trying to write standard C++ with full exception
> I've never particularly run down.
specification in MSVC++, so no surprise here.
> It is certainly simpler to throwOk, let's try to revisit it. The problem is I don't know how well a
> an object that doesn't need to be explicitly deleted. I want to
> replace the SQLException class with an abstract class of the same
> name, so this is a good time to revisit the question.
solution scales to Linux and shared libraries, for example, this is where
your experience counts.
> That said, assuming an class has a virtual destructor, the deleteYes, it will find always the correct destructor, but hopefully better if
> operator is library/program safe.
the virtual tables in the library and the program are in sync. :-)
> Now maybe if we eliminatedThen you are speaking about safe C++, known also as A++ I believe. Or we
> the delete operator in favor of garbage collection,
can have another peek at Objective-C, that runs as a preprocessor. Or we can
switch to Eiffel and have the garbage collector being enabled/disabled at
will... or we can create a SQL-like language to satisfy your needs to avoid
confusion in the reuse of the same reserved words (in that case, we better
go back to GDML).
> eliminatedBecause all methods are virtual by definition, implicitly like Smalltalk?
> non-virtual methods,
> dropped overloaded operators as confusing,I can't agree here even if you send me a check. I like too much name
overloading and operator overloading even if you prefer the only-one-meaning
of SQL. Simply put, procedural and OO languages don't have to be so
castrated as declarative languages.... IMHO of course.
> purge "union" as unsafe,Ah, well, union is only required in very specific code and probably best
avoided or encapsulated deeply in a class implementation. I almost thought
you were speaking about SQL's UNION.
> and required all method to find a homeDon't try to fool us, Jim, you are speaking about Java and no other thing.
> in a class namespace, we could improve the language... C+=2?
> Hot Chocolate?
> Jim Starkey
Let's call Jim++ to avoid further discussions about languages... as you need
time to understand Bill's passion for XML, I need time to understand your
passion for Java.