[firebird-support] Dialect 1 vs. 3: DATE to VARCHAR CAST results in different date/time format

Hello, Executing the following in both, dialect 1 and 3: select cast(current_timestamp as varchar(30))from rdb$database results in a string with a different date/time format. At least on Windows with Firebird 2.5 64-bit. Dialect 1: 7-DEC-2015 20:29:12.3820 Dialect 3: 2015-12-07 20:31:07.2280

Re: [firebird-support] Dialect 1 vs. 3: DATE to VARCHAR CAST results in different date/time format

> On 8-12-2015 09:52, Thomas Steinmaurer t...@iblogmanager.com > [firebird-support] wrote: >> Hello, >> >> Executing the following in both, dialect 1 and 3: >> >> select cast(current_timestamp as varchar(30))from rdb$database >> >> >> results in a string with a different date/time format. At least

Re: [firebird-support] FB lock files

Hi Rudi. Look at this http://www.janus-software.com/fbmanual/manual.php?book=admin=23 Consider to change DefaultDbCachePages in firebird.conf. You should read about this, because it depends if you use super server, classic or super classic. DatabaseGrowthIncrement is a parameter that

Re: [firebird-support] FB lock files

Hi Rudi, You did not provide all required information to give you a reasonable answer. At least, post fb_lock_print -d output. Regards, Alexey Kovyazin Try HQbird now! www.hqbird.com

[firebird-support] UTF8 charset with case insensitive match

I've used FB for years with ISO8859_1 charset and collation. Now I designing a new DB for a big app update in FB3 and wonder about this charset and collation. For test purposes I am using UTF8 and UNICODE_AI_CI and I like that I can now don't have to worry about casing comparisons nor

[firebird-support] Charset UTF8 or ISO8859_1 for new DB with CI + AI

I've used FB for years with ISO8859_1 charset and collation. Now I designing a new DB for a big app update in FB3 and wonder about this charset and collation. My goal is to avoid having to UPPER everything for comparison searches. For test purposes I am using UTF8 and UNICODE_AI_CI and I

Re: [firebird-support] UTF8 charset with case insensitive match

On 12/8/15 2:26 PM, r...@seedsbydesign.com [firebird-support] wrote: > > I've used FB for years with ISO8859_1 charset and collation. > > Now I designing a new DB for a big app update in FB3 and wonder about > this charset and collation. > > For test purposes I am using UTF8 and UNICODE_AI_CI and

Re: [firebird-support] Charset UTF8 or ISO8859_1 for new DB with CI + AI

Guten Tag r...@seedsbydesign.com [firebird-support], > Here are my questions: > 1. Is only one byte used for storage for english and spanish? NO plain englisch will still be one Byte but spanisch (the accented n ) will be multiple bytes > 3. Is there any downside to using UTF8 and

RE: [firebird-support] string difficulty

My bad, should read more carefully. Andrew Zenz From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] Sent: Tuesday, 8 December 2015 6:12 PM To: firebird-support@yahoogroups.com Subject: AW: [firebird-support] string