On 28-6-2012 12:58, the_a_rioch wrote:

>> Logging in Jaybird can be pretty tricky
>
> and it is pity that there are no standard hooks in JDBC/JB/FB that can be used generally.
> Coming back to TS, i still don't know what charset it used to open connection and such.

By default Jaybird will make a connection with characterset NONE. If you
want to use a different characterset (and you usually want that!), you
need to explicitly specify it in the JDBC url (or if you use a
datasource: in the datasource properties).

See appendix A in
http://www.firebirdsql.org/file/documentation/drivers_documentation/Jaybird_2_1_JDBC_driver_manual.pdf

>
>> I have no idea what you mean with this. JAMonAPI is for monitoring
>> application performance.
>
> yes, i understand that is orders more complex tool than just logging.
> but when i searched what i can do to log, there was asuggestion to route app->JAMonAPI->Server-specific-JDBC-provider
>
> Roman Rockitsy few years ago suggester Iron-something, but that is dead and seems to be wiped from the net.
>
>>>> The quickest solution will probably be to extend FirebirdDialect and add
>>>> the following to the constructor:
>>>>
>>>> registerColumnType( Types.LONGVARCHAR, "blob sub_type 1" );
>
> And whole lotta other types.
> I suggested those XPAth examples, for they show different java types, not only -1

I haven't looked at it; I will try to do that next week.

> And there would be half-dozen things to subclass.

Not sure why you would need to subclass half-dozen things. You would
only need to subclass the dialect.

> For what i understand, with UTF8 encoding VarChar is limited to 32KB/4 = 8K chars.
> And there were text fields like 60000 length.
> Don't remember exactly for string fields.
> There were materialized blobs and cblobs.
> And who knows what.
>
>>> Do you know there was some person subclassing FB dialect for JIRA ?
>>> his main problem was long names exceeding 32 length though.
>
>> That would really be something that is out of scope for me.
>
> I don't know if SQL tells something on required names length, but Atlassian products are popular, even FB team uses Jira.

No the SQL standard doesn't say anything about identifier lengths.
However Oracle has the same limitation for identifier lengths as Firebird.

Mark
--
Mark Rotteveel