Suresh Thalamati wrote:
Mike Matrigali wrote:
Mike Matrigali wrote:
Ok, didn't realize this broke the model. As long as the info gets down
to store I don't really care how. So if you can't get the info from
the template we pass down, then we should just add another array
argument to
Mike Matrigali wrote:
Mike Matrigali wrote:
Ok, didn't realize this broke the model. As long as the info gets down
to store I don't really care how. So if you can't get the info from
the template we pass down, then we should just add another array
argument to createConglomerate and creat
Mike Matrigali wrote:
Daniel John Debrunner wrote:
Mamta Satoor wrote:
Mike, thanks for going through the wiki page. Especially, the store
section since I am not too familiar with store code.
Following are my responses
1)Mike:Obtain collation id(type) from DataValueDescriptor(DVD)
thro
Daniel John Debrunner wrote:
Mamta Satoor wrote:
Mike, thanks for going through the wiki page. Especially, the store
section since I am not too familiar with store code.
Following are my responses
1)Mike:Obtain collation id(type) from DataValueDescriptor(DVD) through
DVD.getCollateId metho
Mamta Satoor wrote:
Mike, thanks for going through the wiki page. Especially, the store
section since I am not too familiar with store code.
Following are my responses
1)Mike:Obtain collation id(type) from DataValueDescriptor(DVD) through
DVD.getCollateId method.
The way I had collation in min
No worries, Army. In fact your mail thread brought up the hole in the wiki
page where I was vague about current schema when talking about parameters.
Mamta
On 4/3/07, Army <[EMAIL PROTECTED]> wrote:
Daniel John Debrunner wrote:
>
> I don't see how when the current schema is defined makes a di
Daniel John Debrunner wrote:
I don't see how when the current schema is defined makes a difference as
to if they run without error or not? How does the current schema being a
user schema or a system schema make this statement compile to an error?
// Default schema APP.
PreparedStatem
Army wrote:
Daniel John Debrunner wrote:
I'm a little lost by this. What do these two terms mean to you?
"run correctly"
run without error
"would only work if"
run without error
Sorry for the confusion.
Still confused. :-)
I don't see how when the current schema is defined makes a
Army wrote:
Oops, clicked send too quickly on that last one. Will try this again once I
clarify the terminology in my head, then will post.
Daniel John Debrunner wrote:
I'm a little lost by this. What do these two terms mean to you?
"run correctly"
run without error
"would only
Army wrote:
Army wrote:
Since a parameter maker does not have a "defined" schema, does
"current schema" mean the schema when the statement is prepared, or
the schema when it is executed?
For example I can do the following in JDBC:
// Default schema ("APP").
PreparedStatement ps = conn.pre
Daniel John Debrunner wrote:
I'm a little lost by this. What do these two terms mean to you?
"run correctly"
run without error
"would only work if"
run without error
Sorry for the confusion.
Army
Army wrote:
On the other hand, if the statement is changed to:
// Default schema APP.
PreparedStatement ps = conn.prepareStatement(
"select tablename, tabletype from sys.systables where " +
"CAST (tablename as varchar(128)) = ?");
then it might be better to take "current s
Army, riding on the CAST wagon a little bit more, a user can rewrite the
query as follows and then it won't matter in what schema the query is
getting run.
PreparedStatement ps = conn.prepareStatement(
"select tablename, tabletype from sys.systables where " +
"CAST (tablename as varc
I was leaning towards using the current schema at the prepared time because
I am hoping to do all the collation validation at the compile phase rather
than the execute phase. Picking up the schema at the prepared time will help
me enable that.
Let me look at your following mail a little bit more
Mamta Satoor wrote:
Mike, thanks for going through the wiki page. Especially, the store
section since I am not too familiar with store code.
Following are my responses
1)Mike:Obtain collation id(type) from DataValueDescriptor(DVD) through
DVD.getCollateId method.
The way I had collation in m
Thank you very much for the wiki page, Mamta. It is indeed very helpful!
Mamta Satoor wrote:
The character set of the schema the function is defined in. That keeps it
least confusing and easier for the users to understand.
One question similar to Dan's, except mine is w.r.t:
> 8)JDBC paramet
Army wrote:
Since a parameter maker does not have a "defined" schema, does "current
schema" mean the schema when the statement is prepared, or the schema
when it is executed?
For example I can do the following in JDBC:
// Default schema ("APP").
PreparedStatement ps = conn.prepareStatement
Thanks Army, for going through the wiki page and reviewing it.
I was thinking of using the character set of the schema where the statement
is prepared. Your example demonstrates that from user point of view, this
will be easier to understand and easier for us to document.
I will add your comment
If no objections by the end of the day, then I will go ahead and update the
wiki page for the character set of the user defined functions.
thanks,
Mamta
On 4/3/07, Mamta Satoor <[EMAIL PROTECTED]> wrote:
The character set of the schema the function is defined in. That keeps it
least confusing
http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478
7)For user defined functions' that return character string type, the return type's collation
> will have the same collation as current schema's character set.
The "current schema's" character set, or the character set of t
The character set of the schema the function is defined in. That keeps it
least confusing and easier for the users to understand.
Mamta
On 4/3/07, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478
> 7)For user defined fun
Mike, thanks for going through the wiki page. Especially, the store section
since I am not too familiar with store code.
Following are my responses
1)Mike:Obtain collation id(type) from DataValueDescriptor(DVD) through
DVD.getCollateId method.
The way I had collation in mind, collation type would
I have included some comments based on th following wiki page:
> 6)Store needs a way to determine the collation type for a given DVD.
This collation type will then be saved in the column metadata. Provide
the api on DVD to return the correct collation type.
Just an addition here. The way
23 matches
Mail list logo
