RE: [firebird-support] info

2017-12-22 Thread hv...@users.sourceforge.net [firebird-support] 
> If I try the select, I don’t have any record where realindex is null 
 
 
   Check RDB$INDEX_INACTIVE for non-zero\not-null values
 

 Regards,
 Vlad

RE: [firebird-support] info

2017-12-22 Thread 'Paul Beach' pbe...@mail.ibphoenix.com [firebird-support] 

> If I try the select, I don’t have any record where realindex is null 

Then I would next check the database for any possible problems... corruption 
etc.

http://www.ibphoenix.com/resources/documents/how_to/doc_5

Regards
Paul

RE: [firebird-support] info

2017-12-22 Thread Nico Speleers nico.spele...@carfac.com [firebird-support] 
If I try the select, I don’t have any record where realindex is null

Nico Speleers
Team Lead Analyse & Consultancy





Carfac bvba

[Beschrijving: Beschrijving: Beschrijving: CarfacAS 
(klein)]<http://www.carfac.be/>Driving on experience


Ambachtstraat 8 | 9700 Oudenaarde
Tel. +32 55 23 00 00 | Fax +32 55 31 00 95
nico.spele...@carfac.com<mailto:nico.spele...@carfac.com> | 
www.carfac.be<http://www.carfac.be/>

[Facebook]<http://www.facebook.com/groups/120709181286476/>[LinkedIn]<http://www.linkedin.com/company/hdc-software-nv>[Twitter]<https://twitter.com/carfacbvba>




Van: 'Paul Beach' pbe...@mail.ibphoenix.com [firebird-support] 
[mailto:firebird-support@yahoogroups.com]
Verzonden: vrijdag 22 december 2017 13:16
Aan: firebird-support@yahoogroups.com
Onderwerp: RE: [firebird-support] info



Try the following...

Partner index description not found (175))

internal gds software consistency check (partner index description not found.
Missing index for a primary or a foreign key. The problem may be caused by
physical database corruption or by a bug.

Recovery process:

To find the missing index, use following SELECT statement:

select R.RDB$CONSTRAINT_NAME, R.RDB$INDEX_NAME as REFINDEXNAME,
I.RDB$INDEX_NAME as REALINDEX, I.RDB$RELATION_NAME, I.RDB$INDEX_INACTIVE
from RDB$INDICES I RIGHT
JOIN RDB$RELATION_CONSTRAINTS R on I.RDB$INDEX_NAME = R.RDB$INDEX_NAME
where R.RDB$CONSTRAINT_TYPE = 'FOREIGN KEY'
or R.RDB$CONSTRAINT_TYPE = 'PRIMARY KEY'
order by R.RDB$CONSTRAINT_NAME

The contraint that is missing an index (where column REALINDEX is empty) will be
corrupted. Try and recreate this constraint.

Paul



[Non-text portions of this message have been removed]

RE: [firebird-support] info

2017-12-22 Thread 'Paul Beach' pbe...@mail.ibphoenix.com [firebird-support] 
Try the following...

Partner index description not found (175))

internal gds software consistency check (partner index description not found. 
Missing index for a primary or a foreign key. The problem may be caused by 
physical database corruption or by a bug.

Recovery process:

To find the missing index, use following SELECT statement:

select R.RDB$CONSTRAINT_NAME, R.RDB$INDEX_NAME as REFINDEXNAME,
   I.RDB$INDEX_NAME as REALINDEX, I.RDB$RELATION_NAME, I.RDB$INDEX_INACTIVE
from RDB$INDICES I RIGHT
JOIN RDB$RELATION_CONSTRAINTS R on I.RDB$INDEX_NAME = R.RDB$INDEX_NAME
where R.RDB$CONSTRAINT_TYPE = 'FOREIGN KEY'
   or R.RDB$CONSTRAINT_TYPE = 'PRIMARY KEY'
order by R.RDB$CONSTRAINT_NAME

The contraint that is missing an index (where column REALINDEX is empty) will 
be 
corrupted. Try and recreate this constraint.

Paul

Re: [firebird-support] info

2017-12-22 Thread Mark Rotteveel m...@lawinegevaar.nl [firebird-support] 
On 22-12-2017 10:29, Nico Speleers nico.spele...@carfac.com 
[firebird-support] wrote:

This is the third topic you started with the non-descriptive subject 
"info". In the future, could you please come up with a succinct but 
informative subject when posting? Subjects should summarize your 
question or problem, it will help getting better attention to your 
questions.

Mark
-- 
Mark Rotteveel

Re: [firebird-support] info

2017-12-22 Thread Mark Rotteveel m...@lawinegevaar.nl [firebird-support] 
On 22-12-2017 10:29, Nico Speleers nico.spele...@carfac.com 
[firebird-support] wrote:

> Problem
> Engine Error (code = 335544333): internal Firebird consistency check (partner 
> index description not found (175), file: idx.cpp line: 1271).
> SQL error (code = -902): Unsuccessful execution caused by a system error that 
> precludes successful execution of subsequent statements.
Which version of Firebird are you using (specify the full version, please).

Mark
-- 
Mark Rotteveel

RE: [firebird-support] info

2017-12-22 Thread Nico Speleers nico.spele...@carfac.com [firebird-support] 
Insert into OrderTypeDescriptions (OrderTypeId, OrderTypeDescription, 
LanguageId)
values (1, 'Test', 1)

Nico Speleers
Team Lead Analyse & Consultancy





Carfac bvba

[Beschrijving: Beschrijving: Beschrijving: CarfacAS 
(klein)]Driving on experience


Ambachtstraat 8 | 9700 Oudenaarde
Tel. +32 55 23 00 00 | Fax +32 55 31 00 95
nico.spele...@carfac.com | 
www.carfac.be

[Facebook][LinkedIn][Twitter]




Van: Рустам Муса-Ахунов rusta...@ukr.net [firebird-support] 
[mailto:firebird-support@yahoogroups.com]
Verzonden: vrijdag 22 december 2017 10:38
Aan: firebird-support@yahoogroups.com
Onderwerp: [firebird-support] info



Show you INSERT query for OrderTypeDescriptions table.



[Non-text portions of this message have been removed]

RE: [firebird-support] Info

2017-12-20 Thread 'Zoran' zoran...@gmail.com [firebird-support] 
Hello Helen

 

I understand that we shouldn't mess up with IDENTITY column, as you said. I
have the same problem as original poster and I'm using this code

 

SELECT G.RDB$GENERATOR_NAME

FROM RDB$RELATION_FIELDS AS G

WHERE G.RDB$RELATION_NAME = 'CUSTOMER'

AND G.RDB$FIELD_NAME = (SELECT F.RDB$FIELD_NAME

FROM RDB$INDEX_SEGMENTS AS F

LEFT JOIN RDB$RELATION_CONSTRAINTS AS RC ON
(RC.RDB$INDEX_NAME = F.RDB$INDEX_NAME)

WHERE RC.RDB$RELATION_NAME = 'CUSTOMER'

AND RC.RDB$CONSTRAINT_TYPE = 'PRIMARY KEY')

 

to obtain IDENTITY sequencer name.  Then I increase it to get the next
IDENTITY for master table, which I then populate into master-key columns of
the detail table.

 

Is this approach 'legit'? Will I run into problems in the future (assuming
that RDB$ table structures don't change)?

 

Thanks.

Zoran

 

 

 

 

From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] 
Sent: Tuesday, December 19, 2017 2:29 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Info

 

Hello Nico,

Wednesday, December 20, 2017, 4:34:09 AM, you wrote:

> CREATE TABLE ADDRESSES (
> ID INTEGER GENERATED BY DEFAULT AS IDENTITY NOT NULL,
> ADDRESSNAME VARCHAR(100) COLLATE UNICODE_CI_AI,
.

> Id = 1 / AddressName = Test / ..
> Id = 2 / AddressName = Test2 / ..

> I want to know the next Id number in my table Addresses without an
> insert. In my example it will be 3. I want to reserve (without an
> insert) Id number 3 because someone else can also ask the next Id
> number. In that case it must be id number = 4, because you've got
> Number 1 and 2 in the table and number 3 is reserved.

IDENTITY is just lexical candy, useful when you have a generated id
that fires only on inserts. You can mess around with the start number
to some degree, using DDL commands, but otherwise the underlying
generator (sequence) cannot be manipulated, as the name of the internal
generator for the column is unknown to clients. This is what IDENTITY
is about, in fact.

For any id's that you want to manipulate the way you describe, create
an explicit generator for it, along with a BI trigger for the table to
set the conditions for firing the generator. You can use the NEXT
VALUE FOR  command when you want to capture the next
value without firing the trigger. Generators fire outside the
transaction context of the request so, once a value is fetched, the
generator cannot return the same value again.

Of course, you don't want the trigger to fetch another new value and
overwrite the one you reserved, so you must make your BI trigger
detect whether the INSERT command supplies a value.

Helen Borrie

_._,___

Re: [firebird-support] Info

2017-12-19 Thread Helen Borrie hele...@iinet.net.au [firebird-support] 
Hello Nico,

Wednesday, December 20, 2017, 4:34:09 AM, you wrote:

> CREATE TABLE ADDRESSES (
>   IDINTEGER GENERATED BY DEFAULT AS IDENTITY NOT NULL,
>   ADDRESSNAME   VARCHAR(100) COLLATE UNICODE_CI_AI,


> Id = 1 / AddressName = Test / ..
> Id = 2 / AddressName = Test2 / ..

> I want to know the next Id number in my table Addresses without an
> insert. In my example it will be 3. I want to reserve (without an
> insert) Id number 3 because someone else can also ask the next Id
> number. In that case it must be id  number = 4, because you've got
> Number 1 and 2 in the table and number 3 is reserved.

IDENTITY is just lexical candy, useful when you have a generated id
that fires only on inserts.  You can mess around with the start number
to some degree, using DDL commands, but otherwise the underlying
generator (sequence) cannot be manipulated, as the name of the internal
generator for the column is unknown to clients. This is what IDENTITY
is about, in fact.

For any id's that you want to manipulate the way you describe, create
an explicit generator for it, along with a BI trigger for the table to
set the conditions for firing the generator.  You can use the NEXT
VALUE FOR  command when you want to capture the next
value without firing the trigger.  Generators fire outside the
transaction context of the request so, once a value is fetched, the
generator cannot return the same value again.

Of course, you don't want the trigger to fetch another new value and
overwrite the one you reserved, so you must make your BI trigger
detect whether the INSERT command supplies a value.

Helen Borrie

Re: [firebird-support] Info

2017-12-19 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] 
19.12.2017 16:34, Nico Speleers nico.spele...@carfac.com [firebird-support] 
wrote:
> I want to know the next Id number in my table Addresses without an insert. In 
> my example 
> it will be 3. I want to reserve (without an insert) Id number 3 because 
> someone else can 
> also ask the next Id number. In that case it must be id number = 4, because 
> you've got 
> Number 1 and 2 in the table and number 3 is reserved.
> 
> How can I do that ?

   Use sequence.


-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

Re: [firebird-support] info

2017-01-05 Thread Ann Harrison aharri...@ibphoenix.com [firebird-support] 
On Wed, Jan 4, 2017 at 9:41 AM, Nico Speleers - Carfac BVBA
nico.spele...@carfac.com [firebird-support] <
firebird-support@yahoogroups.com> wrote:

We want to create table- and fieldnames (Firebird 3) in camelcase. If we
> want to write a select statement we have to use quotes around a tablename.
> This is not userfriendly. Is there a way that we don't have to use the
> quotes in SQL-statements ?
> We don't want to create our table- and fieldnames in lowercase or
> uppercase.
>
> OK.  Here's how it works.  You can create a table called TablaRasa with a
create table statement.

Create table TablaRasa ;

You can then reference TablaRasa in any SQL statement like this:

Insert into TablaRasa ;
Select from TablaRasA ;
Update TAblaRAsa ;
Delete from"TABLARASA" ;
Drop table TABLARASA;

You can use any capitalization you want.  However, if you ask Firebird to
Show Tables it
will show you TABLARASA.  The SQL standard specifies that unquoted
identifiers are
case insensitive.  That part of the standard was written in 1982, when
computers were
much slower and memory constrained than modern parking meters.  A later
version of
the standard introduced quoted identifiers which preserve case, allow
special characters
(anything other than numbers, letters, $, and _) and allow overlap between
key words
and identifiers.

InterBase (Firebird's ancestor) implemented case insensitive identifiers by
upper casing
identifiers wherever they were referenced and, specifically, storing the
upper case in
its system tables.  That was a cheap and easy way to handle the problem -
and when
you have (by modern standards) no disk space, no memory, and the computing
power
of an abacus, cheap and easy are good.

For reasons lost in history, when InterBase added quoted identifiers, the
developers
decided just to store the quoted value - without quotes, of course - in the
system tables.
Deciding whether an identifier was quoted or not was simple - a name that
contains a
 character that isn't legal in an unquoted identifier must be a quoted
identifier.
Myself, I would have added a field that indicates whether the name is
quoted or not
and preserved the case of unquoted identifiers right then, but they didn't.
  Users
complained about the ugliness of upper case even then in the 90's.  (Yes,
children,
there were people who cared about appearances that long ago.)

That solution produced the anomaly that a quoted identifier that contains
no characters
outside those allowed in unquoted identifiers behaves like an unquoted
identifier.  While

Create table "TABLA RASA" ;

creates a table that can be referenced only as "TABLA RASA" - quotation
marks required,

The similar statement without the space

Create table "TABLARASA" ;

creates a table that can be referenced as tablarasa, TablaRasa, TAblaRAsa,
etc. And,
inversely, if you create a table with an unquoted identifier, you can
reference it in
quoted upper case - example above.


I don't know how that behavior fits the SQL standard, but it's a minor
violationcompared with
the behavior of MySQL and not terribly dissimilar to PostgreSQL.
PostgreSQL chose to
use lower case as the default because it was prettier and didn't look as if
the code was
SHOUTING at you.  InterBase chose upper case because in some European
languages,
classical French for one, the transformation from lower to upper is
deterministic, but the
translation from upper to lower can produce several results.  Not that we
were all that
far into internationalization in '83, but we were thinking about it.


MySQL chose to use the case rules for the environment it runs in - case
sensitive
on Linux, case insensitive on Windows. Mac/OS had different case rules for
different file
systems.   That looks very natural if you run in a single environment, but
it is a bit of a
bitch if you try to create portable applications.  MySQL also uses
different rules for different
types of identifiers.  You could look it up.  Hell, I'll look it up.

http://dev.mysql.com/doc/refman/5.5/en/identifier-case-sensitivity.html?ff=nopfpls


So, in Firebird, preserving the given case of identifiers in the system
tables would just be
a matter of programming and a change to the system tables which is a bigger
problem
but not out of the scope of a major version. The question is whether that
effort is worth
the price given the challenges of making Firebird more secure, faster, more
reliable, and
more conformant with new SQL features, given the limited programming
resources available.

In sum, handwritten code can use upper and lower case in identifiers
without quotes and
look pretty.  If you want to generate names for triggers and so on from the
original format,
that works too.  Trigger TablaRasaTrigInsert1 is exactly equivalent to
TABLARASATrigInsert1
and you can reference it as either.  Machine generated code can put quotes
around every
name it finds in the system tables and create working ugly code.  The
behavior is standard
compliant and works in

Re: Re: [firebird-support] info

2017-01-05 Thread liviuslivius liviusliv...@poczta.onet.pl [firebird-support] 
Hi,
 
when you migrate something and this is reserved word you name it with quotes, 
and also if it contain space
but i prefer in that migration to change the name instead using double quotes.
But another place where it is vital to have double quotes supported is
select field as "some name for field"
 
regards,
Karol Bieniaszewski
 
W dniu 2017-01-05 12:43:40 użytkownik 'Arno Brinkman' fbsupp...@abvisie.nl 
[firebird-support] <firebird-support@yahoogroups.com> napisał:
 
This "Problem" is listed in the tracker:
http://tracker.firebirdsql.org/browse/CORE-1645
I don't understand who ever though of supporting case-behaviour, why the
hell should i want a table named "ATable" and "atable" and both different
tables.
Anyway this is something what is inherited from the past, let's hope the
firebird developers get some time in the future to solve this.
Kind Regards,
Arno Brinkman
ABVisie
-Oorspronkelijk bericht-
From: Nico Speleers - Carfac BVBA nico.spele...@carfac.com
[firebird-support]
Sent: Thursday, January 5, 2017 10:36 AM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] info
Based on table- and columnnames in camelcase our programmers can automatic
create their objects and classes. Therefore we need to create our table- and
columnnames in camelcase. Another reason is readability. We found camelcase
more readable then UPPERCASE.
Have you got a solution for my problem ?
Nico Speleers
Analyst
Carfac bvba
Driving on experience
Rijksweg 53
9680 Maarkedal
Tel. +32 55 23 00 00
Fax +32 55 31 00 95
nico.spele...@carfac.com
www.carfac.be
-Oorspronkelijk bericht-
Van: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Verzonden: donderdag 5 januari 2017 10:23
Aan: firebird-support@yahoogroups.com
Onderwerp: Re: [firebird-support] info
05.01.2017 8:51, Nico Speleers - Carfac BVBA nico.spele...@carfac.com
[firebird-support]
wrote:
> If I execute Create table MyTable(aField integer) then the tablename is
> saved as MYTABLE.
Why do you care how it is saved? Just don't look into system tables when
writing your
queries.
--
WBR, SD.


++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu
there.
Also search the knowledgebases at
http://www.ibphoenix.com/resources/documents/
++

Yahoo Groups Links

Posted by: Nico Speleers - Carfac BVBA <nico.spele...@carfac.com>

++
Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu. Try FAQ and other links from the left-side menu
there.
Also search the knowledgebases at
http://www.ibphoenix.com/resources/documents/
++

Yahoo Groups Links

 

Re: [firebird-support] info

2017-01-05 Thread Slavomir Skopalik skopa...@elektlabs.cz [firebird-support] 
 FtDateUTC;   
(* UTC timestamp of record insertion *)
 property lDateUTC:TDateTime read FlDateUTC write FlDateUTC;   
(* UTC timestamp of last record modification *)
 end;
 TUSERFUNCTIONSClass=class of TFB_UserFunction;
{$ENDREGION}

Slavek

Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection and evaluation of data from machines and laboratories
by means of system MASA (http://www.elektlabs.cz/m2demo)
-
Address:
Elekt Labs s.r.o.
Chaloupky 158
783 72 Velky Tynec
Czech Republic
---
Mobile: +420 724 207 851
icq:199 118 333
skype:skopaliks
e-mail:skopa...@elektlabs.cz
http://www.elektlabs.cz

On 5.1.2017 10:36, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support] wrote:
> Based on table- and columnnames in camelcase our programmers can automatic 
> create their objects and classes. Therefore we need to create our table- and 
> columnnames in camelcase. Another reason is readability. We found camelcase 
> more readable then UPPERCASE.
>
> Have you got a solution for my problem ?
>
> Nico Speleers
> Analyst
>
>
>
> Carfac bvba
> Driving on experience
>
> Rijksweg 53
> 9680 Maarkedal
> Tel. +32 55 23 00 00
> Fax +32 55 31 00 95
> nico.spele...@carfac.com
> www.carfac.be
>   
>
>
>
>
> -Oorspronkelijk bericht-
> Van: firebird-support@yahoogroups.com 
> [mailto:firebird-support@yahoogroups.com]
> Verzonden: donderdag 5 januari 2017 10:23
> Aan: firebird-support@yahoogroups.com
> Onderwerp: Re: [firebird-support] info
>
> 05.01.2017 8:51, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
> [firebird-support]
> wrote:
>> If I execute Create table MyTable(aField integer) then the tablename is 
>> saved as MYTABLE.
> Why do you care how it is saved? Just don't look into system tables when 
> writing your
> queries.
>
>








++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

Re: [firebird-support] info

2017-01-05 Thread 'Arno Brinkman' fbsupp...@abvisie.nl [firebird-support] 
This "Problem" is listed in the tracker:

http://tracker.firebirdsql.org/browse/CORE-1645

I don't understand who ever though of supporting case-behaviour, why the 
hell should i want a table named "ATable" and "atable" and both different 
tables.
Anyway this is something what is inherited from the past, let's hope the 
firebird developers get some time in the future to solve this.


Kind Regards,
Arno Brinkman
ABVisie



-Oorspronkelijk bericht- 
From: Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support]
Sent: Thursday, January 5, 2017 10:36 AM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] info

Based on table- and columnnames in camelcase our programmers can automatic 
create their objects and classes. Therefore we need to create our table- and 
columnnames in camelcase. Another reason is readability. We found camelcase 
more readable then UPPERCASE.

Have you got a solution for my problem ?

Nico Speleers
Analyst



Carfac bvba
Driving on experience

Rijksweg 53
9680 Maarkedal
Tel. +32 55 23 00 00
Fax +32 55 31 00 95
nico.spele...@carfac.com
www.carfac.be





-Oorspronkelijk bericht-
Van: firebird-support@yahoogroups.com 
[mailto:firebird-support@yahoogroups.com]
Verzonden: donderdag 5 januari 2017 10:23
Aan: firebird-support@yahoogroups.com
Onderwerp: Re: [firebird-support] info

05.01.2017 8:51, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support]
wrote:
> If I execute Create table MyTable(aField integer) then the tablename is 
> saved as MYTABLE.

   Why do you care how it is saved? Just don't look into system tables when 
writing your
queries.


-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu 
there.

Also search the knowledgebases at 
http://www.ibphoenix.com/resources/documents/

++


Yahoo Groups Links






Posted by: Nico Speleers - Carfac BVBA <nico.spele...@carfac.com>


++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu 
there.

Also search the knowledgebases at 
http://www.ibphoenix.com/resources/documents/

++


Yahoo Groups Links

Re: [firebird-support] info

2017-01-05 Thread 'Martijn Tonies (Upscene Productions)' m.ton...@upscene.com [firebird-support] 
Hello Nico,

>I want to create a tablename in camelcase without using quotes.
>
>If I execute Create table MyTable(aField integer) then the tablename is 
>saved as MYTABLE. And yes then you can use camelcase >without quotes.
>
>Can you find a solution ?

The only solution to preserving case, is to use double quotes around the 
object names.




With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Database Workbench - developer tool for Oracle, MS SQL Server, PostgreSQL,
SQL Anywhere, MySQL, InterBase, NexusDB and Firebird.

Re: [firebird-support] info

2017-01-05 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] 
05.01.2017 10:36, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support] 
wrote:
> Have you got a solution for my problem ?

   There is no solution for your problem.


-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

RE: [firebird-support] info

2017-01-05 Thread Nico Speleers - Carfac BVBA nico.spele...@carfac.com [firebird-support] 
Based on table- and columnnames in camelcase our programmers can automatic 
create their objects and classes. Therefore we need to create our table- and 
columnnames in camelcase. Another reason is readability. We found camelcase 
more readable then UPPERCASE.

Have you got a solution for my problem ?

Nico Speleers
Analyst



Carfac bvba
Driving on experience

Rijksweg 53
9680 Maarkedal
Tel. +32 55 23 00 00
Fax +32 55 31 00 95
nico.spele...@carfac.com
www.carfac.be
 




-Oorspronkelijk bericht-
Van: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] 
Verzonden: donderdag 5 januari 2017 10:23
Aan: firebird-support@yahoogroups.com
Onderwerp: Re: [firebird-support] info

05.01.2017 8:51, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support] 
wrote:
> If I execute Create table MyTable(aField integer) then the tablename is saved 
> as MYTABLE.

   Why do you care how it is saved? Just don't look into system tables when 
writing your 
queries.


-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

Re: [firebird-support] info

2017-01-05 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] 
05.01.2017 8:51, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support] 
wrote:
> If I execute Create table MyTable(aField integer) then the tablename is saved 
> as MYTABLE.

   Why do you care how it is saved? Just don't look into system tables when 
writing your 
queries.


-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/

RE: [firebird-support] info

2017-01-04 Thread Nico Speleers - Carfac BVBA nico.spele...@carfac.com [firebird-support] 
I want to create a tablename in camelcase without using quotes. 

If I execute Create table MyTable(aField integer) then the tablename is saved 
as MYTABLE. And yes then you can use camelcase without quotes.

Can you find a solution ?

Nico Speleers
Analyst

Carfac bvba
Driving on experience

Rijksweg 53
9680 Maarkedal
Tel. +32 55 23 00 00
Fax +32 55 31 00 95
nico.spele...@carfac.com
www.carfac.be
 



-Oorspronkelijk bericht-
Van: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] 
Verzonden: woensdag 4 januari 2017 15:48
Aan: firebird-support@yahoogroups.com
Onderwerp: Re: [firebird-support] info

04.01.2017 15:41, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support]
wrote:
> We want to create table- and fieldnames (Firebird 3) in camelcase. If 
> we want to write a select statement we have to use quotes around a 
> tablename. This is not userfriendly. Is there a way that we don't have to use 
> the quotes in SQL-statements ?

   Just don't use double quotes:

Create table MyTable(aField integer);
Select aField from MyTable;

   No problem if you write queries by hand.
   On other hand, if you use a visual query builder, you'll have no problem 
with double quotes.

-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item on the main 
(top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

Re: [firebird-support] info

2017-01-04 Thread 'Martijn Tonies (Upscene Productions)' m.ton...@upscene.com [firebird-support] 
Hello Nico,

If you want the case preserved, you have to use double quotes, always.


With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Database Workbench - developer tool for Oracle, MS SQL Server, PostgreSQL,
SQL Anywhere, MySQL, InterBase, NexusDB and Firebird.

We want to create table- and fieldnames (Firebird 3) in camelcase. If we 
want to write a select statement we have to use quotes around a tablename. 
This is not userfriendly. Is there a way that we don't have to use the 
quotes in SQL-statements ?
We don't want to create our table- and fieldnames in lowercase or uppercase.

Nico Speleers
Analyst





Carfac bvba

Driving on experience


Rijksweg 53
9680 Maarkedal
Tel. +32 55 23 00 00
Fax +32 55 31 00 95
nico.spele...@carfac.com
www.carfac.be
[cid:image001.jpg@01D11613.C23F19C0][cid:image002.jpg@01D11613.C23F19C0]
 
[cid:image003.jpg@01D11613.C23F19C0] 

[Beschrijving: Beschrijving: Beschrijving: CarfacAS 
(klein)]


)


[Non-text portions of this message have been removed]




Posted by: Nico Speleers - Carfac BVBA 


++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu 
there.

Also search the knowledgebases at 
http://www.ibphoenix.com/resources/documents/

++


Yahoo Groups Links

Re: [firebird-support] info

2017-01-04 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] 
04.01.2017 15:41, Nico Speleers - Carfac BVBA nico.spele...@carfac.com 
[firebird-support] 
wrote:
> We want to create table- and fieldnames (Firebird 3) in camelcase. If we want 
> to write a
> select statement we have to use quotes around a tablename. This is not 
> userfriendly. Is
> there a way that we don't have to use the quotes in SQL-statements ?

   Just don't use double quotes:

Create table MyTable(aField integer);
Select aField from MyTable;

   No problem if you write queries by hand.
   On other hand, if you use a visual query builder, you'll have no problem 
with double 
quotes.

-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/