On Fri, 06 Jul 2012 09:45:06 +0200, Dimitry Sibiryakov s...@ibphoenix.com
wrote:
How about isc_create_database()? Should it follow the same rules?
It probably should.
But if we'd go this route, one more idea comes to mind. What about
prohibiting NONE as a default database charset at all,
06.07.2012 11:45, Dimitry Sibiryakov wrote:
How about isc_create_database()? Should it follow the same rules?
Sure.
Shouldn't it be coupled with prohibiting declaration of charset for single
fields?
Currently nothing prevent (me) from creating database with default charset
NONE and set
06.07.2012 11:54, Mark Rotteveel wrote:
I am not sure I see why you would need to prohibit setting the
characterset of a specific field when requiring the default characterset to
be set. Could you explain the reasoning on that?
I believe his was referring to the default charset being set to
On Fri, 06 Jul 2012 10:20:13 +0200, Dimitry Sibiryakov s...@ibphoenix.com
wrote:
I have a script which creates my tables in my own just created
database
or any existing
user-choosen database. Because I can't predict default character set of
such user
database, all fields in this script
06.07.2012 12:20, Dimitry Sibiryakov wrote:
I have a script which creates my tables in my own just created database or
any existing
user-choosen database. Because I can't predict default character set of such
user
database, all fields in this script are created with explicit character set
06.07.2012 10:33, Dmitry Yemanov wrote:
So you mean that the database is created before it becomes known what is
the application charset, right?
Not quite so. Actually, I don't care about data character set at all. That's
the case
where charset NONE fits perfectly.
--
WBR, SD.
On 05/07/2012 09:50, Stefan Heymann wrote:
After some hot discussion in Firebird-Java, I want to propose to ditch
the NONE as default character set for newly created databases when no
database charset is specified.
The server/engine should read the config file and use the default
character
After some hot discussion in Firebird-Java, I want to propose to ditch
the NONE as default character set for newly created databases when no
database charset is specified.
That hot and overly long discussion mentioned started with http://
30.06.2012 0:02, Leyne, Sean wrote:
I would say make the Default 8K since that is the typical disk block size of
modern HDD.
I tend to agree.
Current HDDs are also an argument to make the minimum page size 4K, since
that is the physical sector size for the 2TB+ HDDs.
The minimum is 4K
Hi,
After some hot discussion in Firebird-Java, I want to propose to ditch
the NONE as default character set for newly created databases when no
database charset is specified.
The server/engine should read the config file and use the default
character set which is specified there. The
On 29/06/2012 09:27, Roman Rokytskyy wrote:
Hi,
After some hot discussion in Firebird-Java, I want to propose to ditch
the NONE as default character set for newly created databases when no
database charset is specified.
The server/engine should read the config file and use the default
Without default client charset too, this is a partial solution. Not all
applications are written in Java and .NET.
Sure, but defaulting should not happen in fbclient.dll, but in the FB
access library, IBPP for C++, UIB or whatever components are currently
used in Delphi. AFAIK, Delphi is
The only change is that newly created databases are created with some
meaningful charset, not with raw data. The rest remains as it is now -
those that want to manage it already, will be able to do this.
In this case why to configure the default? Let's hardcode it to UTF-8!
Yes, increase
The only change is that newly created databases are created with some
meaningful charset, not with raw data. The rest remains as it is
now - those that want to manage it already, will be able to do this.
In this case why to configure the default? Let's hardcode it to UTF-8!
Yes,
14 matches
Mail list logo
