firebird-odbc-devel — All about development of Firebird ODBC driver donated by IBPhoenix

Re: [Firebird-odbc-devel] [Fwd: Fwd: Ports needed to connect]

[Jano P. <jan...@gm...>]

Hi Ken,

There is only one port required to be open for connection to succeed - and
by default this is 3050.

The problem is likely with the firewall rule. This link has some details
about setting up firewall in WinXP SP2.

http://mc-computing.com/Databases/Firebird/Port_3050.html

Maybe try testing with some simple client (such as telnet command line
utility) connecting to port 3050 and see if it connects when firewall is on
and configured. If not, try tweaking the firewall rule untill connection can
be established.


--
Jano



On 28 April 2010 07:32, Ann W. Harrison <aha...@ib...> wrote:

>
> From: Ken Buska <kb...@co...>
> Date: Tue, Apr 27, 2010 at 1:40 PM
> Subject: Ports needed to connect
> To: fir...@li...
>
>
> I have a customer who wants to connect to our database using the odbc
> connector on his machine. What ports need to be open besides 3050 in order
> for the ODBC connector to connect to the Firebird Server? I'm able to
> connect fine with windows firewall disabled but connection fails with only
> port 3050 open.
>
> Cheers,
> Ken
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>

[Firebird-odbc-devel] Ports needed to connect

[Ken B. <kb...@co...>]

I have a customer who wants to connect to our database using the odbc
connector on his machine. What ports need to be open besides 3050 in order
for the ODBC connector to connect to the Firebird Server? I'm able to
connect fine with windows firewall disabled but connection fails with only
port 3050 open.

Cheers,
Ken

[Firebird-odbc-devel] [Fwd: Fwd: Ports needed to connect]

[Ann W. H. <aha...@ib...>]

From: Ken Buska <kb...@co...>
Date: Tue, Apr 27, 2010 at 1:40 PM
Subject: Ports needed to connect
To: fir...@li...


I have a customer who wants to connect to our database using the odbc
connector on his machine. What ports need to be open besides 3050 in order
for the ODBC connector to connect to the Firebird Server? I'm able to
connect fine with windows firewall disabled but connection fails with only
port 3050 open.

Cheers,
Ken

Re: [Firebird-odbc-devel] Firebird 2.1 ODBC Numeric and Date fields.

[André K. C. <Kna...@be...>]

This might be a stupid question, but did you make sure that your
version of employee.fdb is indeed also dialect 3?




~~~Ihre Nachricht~~~

SC> Hi People,

SC> I am using Perl on Linux (Kubuntu 9.10) with Firebird 2.1.  I wanted to use
SC> ODBC, but in the end I gave up using it because I couldn't get the DATE or
SC> number formats to work.  Instead I used the DBI::Interbase driver, while it
SC> works, it is subject to occasional crashes, so I'd like to go back to trying
SC> ODBC.

SC> My current problem is that if I use isql on employee.fbd, (eg select first 1
SC> change_date from salary_history), I get:

SC> 1992-12-15 00:00:00. (Data type timestamp)

SC> if I use it on my own database, (eg select first 1
SC> att_patient_examination_ddt from tbl_patient_exam), I get:

SC> 22256-10-18.  (Data type date)

SC> Any ideas what I could do?

SC> Well, actually, writing that last bit has helped.  If I change from a DATE
SC> data type to a TIMESTAMP, it seems to work, but now I need to check time
SC> fields and number fields.  Surely the DATE format should work?  What do I
SC> need to do to fix this (NB Flamerobin has no such problems on the same
SC> field)?  I am also encoutering other sporadic problems such as a read being
SC> successful one moment and unsuccessful the next?  Is this a known problem?

SC> Regards

SC> Steve

SC> The odbcinst.ini file entry is:

SC> [Firebird]
SC> Description             = Firebird/InterBase(r) driver
SC> Driver          = /usr/lib/libOdbcFb.so
SC> Setup           = /usr/lib/libOdbcFb.so
SC> UsageCount              = 2

SC> The odbc.ini file entries are:

SC> [END_DB]
SC> Description = Firebird
SC> Driver = Firebird
SC> Dbname = localhost:/home/steve/Documents/Endoscopia/DB/ENDOSCOPIA.FDB
SC> Client          =
SC> User = SYSDBA
SC> Password = masterkey
SC> Role            =
SC> CharacterSet    = NONE
SC> ReadOnly        = No
SC> NoWait          = No
SC> Dialect         = 3
SC> QuotedIdentifier        = Yes
SC> SensitiveIdentifier     = No
SC> AutoQuotedIdentifier    = No

SC> [Employee]
SC> Description = Firebird
SC> Driver = Firebird
SC> Dbname = localhost:/home/steve/Documents/employee.fdb
SC> Client          =
SC> User = SYSDBA
SC> Password = masterkey
SC> Role            =
SC> CharacterSet    = NONE
SC> ReadOnly        = No
SC> NoWait          = No
SC> Dialect         = 3
SC> QuotedIdentifier        = Yes
SC> SensitiveIdentifier     = No
SC> AutoQuotedIdentifier    = No





SC> ------------------------------------------------------------------------------
SC> Download Intel® Parallel Studio Eval
SC> Try the new software tools for yourself. Speed compiling, find bugs
SC> proactively, and fine-tune applications for parallel performance.
SC> See why Intel Parallel Studio got high marks during beta.
SC> http://p.sf.net/sfu/intel-sw-dev
SC> _______________________________________________
SC> Firebird-odbc-devel mailing list
SC> Fir...@li...
SC> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

---

[Firebird-odbc-devel] Firebird 2.1 ODBC Numeric and Date fields.

[Steve C. <ste...@sc...>]

Hi People,

I am using Perl on Linux (Kubuntu 9.10) with Firebird 2.1.  I wanted to use
ODBC, but in the end I gave up using it because I couldn't get the DATE or
number formats to work.  Instead I used the DBI::Interbase driver, while it
works, it is subject to occasional crashes, so I'd like to go back to trying
ODBC.

My current problem is that if I use isql on employee.fbd, (eg select first 1
change_date from salary_history), I get:

1992-12-15 00:00:00. (Data type timestamp)

if I use it on my own database, (eg select first 1
att_patient_examination_ddt from tbl_patient_exam), I get:

22256-10-18.  (Data type date)

Any ideas what I could do?

Well, actually, writing that last bit has helped.  If I change from a DATE
data type to a TIMESTAMP, it seems to work, but now I need to check time
fields and number fields.  Surely the DATE format should work?  What do I
need to do to fix this (NB Flamerobin has no such problems on the same
field)?  I am also encoutering other sporadic problems such as a read being
successful one moment and unsuccessful the next?  Is this a known problem?

Regards

Steve

The odbcinst.ini file entry is:

[Firebird]
Description		= Firebird/InterBase(r) driver
Driver		= /usr/lib/libOdbcFb.so
Setup		= /usr/lib/libOdbcFb.so
UsageCount		= 2

The odbc.ini file entries are:

[END_DB]
Description = Firebird
Driver = Firebird
Dbname = localhost:/home/steve/Documents/Endoscopia/DB/ENDOSCOPIA.FDB
Client          =
User = SYSDBA
Password = masterkey
Role            =
CharacterSet    = NONE
ReadOnly        = No
NoWait          = No
Dialect         = 3
QuotedIdentifier        = Yes
SensitiveIdentifier     = No
AutoQuotedIdentifier    = No

[Employee]
Description = Firebird
Driver = Firebird
Dbname = localhost:/home/steve/Documents/employee.fdb
Client          =
User = SYSDBA
Password = masterkey
Role            =
CharacterSet    = NONE
ReadOnly        = No
NoWait          = No
Dialect         = 3
QuotedIdentifier        = Yes
SensitiveIdentifier     = No
AutoQuotedIdentifier    = No

[Firebird-odbc-devel] encryption and SSL?

[Liz W. <li...@li...>]

Hello,

I am researching Firebird ODBC driver encryption support. There are two 
areas of functionality I am interested in:

1) Encrypting the username/password credentials in the connection 
string. All other communication could be unencrypted.

2) Full SSL support, encrypting all ODBC communication.

Is there an ODBC driver for Firebird that supports either of these 
functions? If not, are there any plans to implement?

Thank you,
Liz

[Firebird-odbc-devel] Ruby FB 2.0 driver

[Harvey S. <hs...@ta...>]

Hi

 

Is there a stabile driver for Ruby and Firebird v.2.0 and up available?

 


Harvey Shaw
Developer

	
	

 

Re: [Firebird-odbc-devel] Error in parsing transaction settings ?!

[Nikolay S. <nik...@re...>]

Hello, Marco!

1) Can you open this issue in a tracker? Test case would be welcome there.

2) Is it possible for you to prepare "unified context diff" (diff -u) 
format patch against current HEAD?

I will review/apply it afterwards.

Thanks!

Nikolay Samofatov

On 15.02.2010 11:22, Marco Held wrote:
>
> Hello all,
>
> due to I had some problem with transaction setting I ran through the 
> code by debugger  and found the following function which maybe did not 
> work like it should. It is used to parse a "set transaction" command 
> and check if some tables are required to be used in a special 
> reservation mode.
>
> According to the sql syntax declaration
>
> /Syntax /SET TRANSACTION [NAME transaction]
>
> [READ WRITE | READ ONLY]
>
> [WAIT | NO WAIT]
>
> [[ISOLATION LEVEL] {SNAPSHOT [TABLE STABILITY]
>
> | READ COMMITTED [[NO] RECORD_VERSION]}]
>
> [RESERVING <reserving_clause>
>
> | USING dbhandle [, dbhandle ...]];
>
> <reserving_clause> = table [, table ...]
>
> [FOR [SHARED | PROTECTED] {READ | WRITE}] [, <reserving_clause>]
>
> it is possible to define several tables in a comma separated list for 
> a special reserving mode. The function below does not respect this 
> possibility in my opinion. Only the comma for separation of different 
> "FOR" clauses is respected.
>
> Furthermore there seems to be a problem in setting the "lockMode" for 
> the table. Within the last "if" section for all tables found during 
> the parsing, the "lockMode" of the last "FOR" clause is set. So the 
> possibility of having different "lockMode" for each "FOR" clause is 
> not respected.
>
> void IscConnection::parseReservingTable( char *& string, char *& 
> tpbBuffer, short transFlags )
>
> {
>
> char *saveLockMode[256];
>
> int countTable = 0;
>
> char lockMode = 0;
>
> char *& ptOut = string;
>
> char *beg = tpbBuffer + 2;
>
> char *end;
>
> while ( true )
>
> {
>
>             saveLockMode[countTable++] = beg - 2;
>
> char &lengthTableName = *(beg - 1);
>
>             end = beg;
>
> while ( !IS_END_TOKEN( *ptOut ) )
>
> *end++ = *ptOut++;
>
>             lengthTableName = end - beg;
>
>             SKIP_WHITE ( ptOut );
>
> //          SYNTAX_ERROR ("relation name");
>
> char &lockLevel = *end++;
>
>             IS_MATCH_EXT( "FOR" );
>
>             lockLevel = (transFlags & TRA_con) ? isc_tpb_protected : 
> isc_tpb_shared;
>
>             lockMode = isc_tpb_lock_read;
>
> if ( IS_MATCH_EXT( "PROTECTED" ) )
>
>                   lockLevel = isc_tpb_protected;
>
> else if ( IS_MATCH_EXT( "EXCLUSIVE" ) )
>
>                   lockLevel = isc_tpb_exclusive;
>
> else if ( IS_MATCH_EXT( "SHARED" ) )
>
>                   lockLevel = isc_tpb_shared;
>
> if ( IS_MATCH_EXT( "WRITE" ) )
>
> {
>
> if ( transFlags & TRA_ro )
>
> throw SQLEXCEPTION( SYNTAX_ERROR, "write lock requested for a 
> read_only transaction" );
>
>                   lockMode = isc_tpb_lock_write;
>
> }
>
> else
>
>                   IS_MATCH_EXT( "READ" );
>
> if ( !( IS_MATCH_EXT( "," ) ) )
>
> break;
>
>             beg = end + 2;
>
> }
>
>       tpbBuffer = end;
>
> if ( countTable )
>
> {
>
> //
>
> // get the lock level and mode and apply them to all the
>
> // relations in the list
>
> //
>
> do
>
> *saveLockMode[--countTable] = lockMode;
>
> while ( countTable );
>
> }
>
> }
>
> Can some authorized person check fix this, please?
>
> Thanks for help!
>
> Regards,
>
> Marco Held
>
> phone: +49 271 77202 27
>
> e-mail: mh...@de... <mailto:mh...@de...>
>
> demig Prozessautomatisierung GmbH -- http://www.demig.de 
> <http://www.demig.de/> -- in...@de... <mailto:in...@de...>
>
> Haardtstraße 40 -- D-57076 Siegen -- Tel. +49 271 77202 0  --  Fax +49 
> 271 77202 92
>
> Registergericht Siegen HRB 2819 -- Geschäftsführer Joachim Herbst, 
> Winfried Held
>

[Firebird-odbc-devel] ERROR[HY000][ODBC Firebird Driver][Firebird]no permission for read/select access to TABLE

[Marius P. <mar...@qb...>]

I developed a Web site using a Firebird database. The VB.NET program reads
from the database via ODBC connection.

When running from Visual Studio 2008, everything works fine. The program
(VB.NET) connects and queries the Firebird Database OK.

I then published the Web Site in the inetpub/wwwroot folder and browse it
with IIS. Now I get an exception:

ERROR[HY000][ODBC Firebird Driver][Firebird]no permission for read/select
access to TABLE CONTACT

(CONTACT is the name of my table)

The ODBC connection was created via Control Panel. It only specifies the
database path, no user name and password. The database registration in Flame
Robin is with "trusted user authentication" (no user name and password).

Why is it working from Visual Studio and not after publishing it?

How is it possible that Firebird ODBC driver does not have permission to
READ from a Firebird database?

Below is the response from Helen Borrie, who recommends I join this group.

Regards

 

Marius Popescu

QBuild Software

 C   O   R   P   O   R   A   T   I   O   N 


145 Renfrew Drive, Markham, ON L3R 9R6, CANADA
Phone +1 905 479 7811 EXT 64  

Email: mar...@qb...
<mailto:geo...@qb...> 

 

Helen Borrie wrote:

It happens because you have not passed a user name in the connection
parameters. 

When you use the fbclient that is in fbembed.dll, your client layer does not
need to pass username and password in the connection string in order to
connect to the database via the server that is embedded in fbembed.dll. This
works, because on Windows the embedded client-server connection does not
perform server-level authentication. However, if you do not supply a user
name, the client layer will pass just NONE or an empty string (depending on
Firebird version). 

However, SQL access privileges are based *in the database*. The situation
you have here is that the user name (CURRENT_USER is NONE or an empty
string) and the database has no privileges stored for NONE. 

All you need to do to fix this is configure the connection to pass the user
name of the user (in RDB$USER_PRIVILEGES in your database) that has the
required access privileges that your application requires. If you don't know
how to do that for the ODBC driver that you are using, please ask on the
forum for that driver. 

-- If it is the Firebird driver, the forum is
fir...@li...
<mailto:firebird-odbc-devel%40lists.sourceforge.net> . You can subscribe
from here: http://firebirdsql.org/index.php?op=lists#fb-odbc-devel

-- If it is a different driver, look in the vendor documentation for a
contact address for the forum for that driver

^ heLen ^

 

 

Re: [Firebird-odbc-devel] Problem with special transaction settings

[Marco H. <mh...@de...>]

Hi Paul,

as you suggested I run the driver through a debugger and found the problem:

In my "set transaction" sql command I defined the table names which should
be RESERVED in lower case letters. Due to these names are used in some
"transaction parameter block" and not put in upper case before as it is
needed, the error raises. If I write them in upper case the wrong behavior
did not happen.

Now I ask if it is possible to do a case conversion within the driver?
Can anybody do this, due to I am not involved fully in the project. 
Maybe it must be done here:

IscConnection.cpp:
IscConnection::parseReservingTable(...) 


Thanks in advance!

Marco Held

phone: +49 271 77202 27
e-mail:  mh...@de...

demig Prozessautomatisierung GmbH – http://www.demig.de – in...@de...
Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
77202 92
Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
Held



-----Ursprüngliche Nachricht-----
Von: Paul Reeves [mailto:pr...@ib...] 
Gesendet: Dienstag, 19. Januar 2010 08:16
An: fir...@li...
Betreff: Re: [Firebird-odbc-devel] Problem with special transaction settings

On Monday 18 January 2010, Marco Held wrote:
> Hi Paul,
>
> thanks for your reply, but what is the sense at all?! I have to look for
> a solution by myself or will it be fixed soon?
>

I was suggesting that you try running the driver through a debugger to see 
if you can locate the cause of the problem. You are using a transaction 
isolation which is uncommon, so this bug could have been there for a long 
time. 


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

----------------------------------------------------------------------------
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for
Conference
attendees to learn about information security's most important issues
through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

[Firebird-odbc-devel] Error in parsing transaction settings ?!

[Marco H. <mh...@de...>]

Hello all,

 

due to I had some problem with transaction setting I ran through the code by
debugger  and found the following function which maybe did not work like it
should. It is used to parse a “set transaction” command and check if some
tables are required to be used in a special reservation mode.

 

According to the sql syntax declaration

Syntax SET TRANSACTION [NAME transaction]

[READ WRITE | READ ONLY]

[WAIT | NO WAIT]

[[ISOLATION LEVEL] {SNAPSHOT [TABLE STABILITY]

| READ COMMITTED [[NO] RECORD_VERSION]}]

[RESERVING <reserving_clause>

| USING dbhandle [, dbhandle …]];

<reserving_clause> = table [, table …]

[FOR [SHARED | PROTECTED] {READ | WRITE}] [, <reserving_clause>]

 

it is possible to define several tables in a comma separated list for a
special reserving mode. The function below does not respect this possibility
in my opinion. Only the comma for separation of different “FOR” clauses is
respected.

Furthermore there seems to be a problem in setting the “lockMode” for the
table. Within the last “if“ section for all tables found during the parsing,
the “lockMode” of the last “FOR” clause is set. So the possibility of having
different “lockMode” for each “FOR” clause is not respected.

 

 

 

void IscConnection::parseReservingTable( char *& string, char *& tpbBuffer,
short transFlags )

{

      char *saveLockMode[256];

      int countTable = 0;

      char lockMode = 0;

      char *& ptOut = string;

      char *beg = tpbBuffer + 2;

      char *end;

 

      while ( true )

    {

            saveLockMode[countTable++] = beg - 2;

            char &lengthTableName = *(beg - 1);

            end = beg;

 

            while ( !IS_END_TOKEN( *ptOut ) )

                  *end++ = *ptOut++;

 

            lengthTableName = end - beg;

 

            SKIP_WHITE ( ptOut );

      //          SYNTAX_ERROR ("relation name");

 

            char &lockLevel = *end++;

 

            IS_MATCH_EXT( "FOR" );

            lockLevel = (transFlags & TRA_con) ? isc_tpb_protected :
isc_tpb_shared;

            lockMode = isc_tpb_lock_read;

 

            if ( IS_MATCH_EXT( "PROTECTED" ) )

                  lockLevel = isc_tpb_protected;

            else if ( IS_MATCH_EXT( "EXCLUSIVE" ) )

                  lockLevel = isc_tpb_exclusive;

            else if ( IS_MATCH_EXT( "SHARED" ) )

                  lockLevel = isc_tpb_shared;

 

            if ( IS_MATCH_EXT( "WRITE" ) )

            {

                  if ( transFlags & TRA_ro )

                        throw SQLEXCEPTION( SYNTAX_ERROR, "write lock
requested for a read_only transaction" );

 

                  lockMode = isc_tpb_lock_write;

            }

            else 

                  IS_MATCH_EXT( "READ" );

 

            if ( !( IS_MATCH_EXT( "," ) ) )

                  break;

 

            beg = end + 2;

      }

 

      tpbBuffer = end;

 

      if ( countTable )

      {

            //

            // get the lock level and mode and apply them to all the

            // relations in the list

            //

            do

                  *saveLockMode[--countTable] = lockMode;

            while ( countTable );

      }

}

 

 

Can some authorized person check fix this, please?

Thanks for help!

 

Regards,

 

Marco Held

 

phone: +49 271 77202 27

e-mail:   <mailto:mh...@de...> mh...@de...

 

demig Prozessautomatisierung GmbH –  <http://www.demig.de/>
http://www.demig.de –  <mailto:in...@de...> in...@de...

Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
77202 92

Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
Held

 

 

[Firebird-odbc-devel] Problems using ODBC Driver

[Irk P. <Pet...@br...>]

Hi,

 

I'm getting the error "sqlcode -904, fbcode 335544792" - Cannot attach
to services manager when I want to use a Firebird ODBC Service.

 

The Test Connection works, but when I cannot connect to the database via
SAP Business Connector.

 

Has anyone an idea, what the problem could be?

 

Best regards,

Peter

 

 

Re: [Firebird-odbc-devel] ODBC driver on 64-bit linux

[Bill G. <bg...@co...>]

Hi Dmitry,

Thanks for taking a look at this.

I guess I gave the wrong impression with my post. I don't have any 
problem building the
driver-- only when I try to use it. Specifically, I get an error at 
execution time when I do a simple test
that tries to insert two integer fields into a relation. I'll try to 
clean up my example and post it.

As for -DSIZEOF_LONG=8, I think that *is* being defined but is not 
necessarily required to
be defined in makefile.linux. Here is what I mean. If I look at the top 
of /usr/include/sqltypes.h,
on my Redhat system, I see these lines.

#ifndef SIZEOF_LONG
# if defined(__alpha) || defined(__sparcv9) || defined(__LP64__) || 
(defined(__HOS_AIX__) && defined(_LP64))
# define SIZEOF_LONG        8
#else
# define SIZEOF_LONG        4
#endif
#endif

With g++ -m64, __LP64__ is automatically defined so SIZEOF_LONG        8 
is also defined

SIZEOF_LONG ==8 insures that SQLINTEGER is a 4-byte quantity.

Bill


Dmitry Starodubov wrote:
> Hi, Bill.
>
> I used gcc-4.1.1 for building Odbc B2_0_0 (v. 149) without errors. I 
> just ran makefile -f makefile.linux and get libOdbcFb.so.
> What kind of error you get when build driver using original makefile?
>
> As Firebird uses 4-byte LONG I don't think that -DSIZEOF_LONG=8 is a 
> good idea.
>
>   
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 9.0.725 / Virus Database: 270.14.137/2617 - Release Date: 01/12/10 14:35:00
>
>   

Re: [Firebird-odbc-devel] ODBC driver on 64-bit linux

[Bill G. <bg...@co...>]

Thanks for taking a look at this.

I looked at that section of sqltypes.h also.
My biggest concern was the case where

SIZEOF_LONG was not defined to be 8
(even though it should be with g++ 4 on linux with -m64).

In that case, SQLINTEGER has 8 bytes. And I assume this is
bad.

I'm going to keep plugging away at this and, if successful,
I'll report back to the list. I'll also submit any patches
if necessary.

Bill

Re: [Firebird-odbc-devel] ODBC driver on 64-bit linux

[Dmitry S. <dmi...@re...>]

Hi, Bill.

I used gcc-4.1.1 for building Odbc B2_0_0 (v. 149) without errors. I 
just ran makefile -f makefile.linux and get libOdbcFb.so.
What kind of error you get when build driver using original makefile?

As Firebird uses 4-byte LONG I don't think that -DSIZEOF_LONG=8 is a 
good idea.

-- 
Dmitry Starodubov,
Red Soft Corporation

Re: [Firebird-odbc-devel] ODBC driver on 64-bit linux

[Paul R. <pr...@ib...>]

On Monday 18 January 2010, Bill Greene wrote:
>
> Before continuing my debugging, I just thought I'd see if anyone could
> give me some specific
> advice. Can anyone who has successfully built a 64-bit linux driver tell
> me if my addition of
> -DBUILD_REAL_64_BIT_MODE -DSIZEOF_LONG=8 is the right thing to do (I do
> know that the sizeof(long) with g++ 4.1.2 -m64 is 8, of course)?
>

Here is an edited (and indented) extract from sqltypes.h:


#if (SIZEOF_LONG == 8)
  #ifndef BUILD_REAL_64_BIT_MODE
    typedef int             SQLINTEGER;
    typedef unsigned int    SQLUINTEGER;
    #define SQLLEN          SQLINTEGER
    #define SQLULEN         SQLUINTEGER
    #define SQLSETPOSIROW   SQLUSMALLINT
    ...
  #else
    typedef int             SQLINTEGER;
    typedef unsigned int    SQLUINTEGER;
    typedef long            SQLLEN;
    typedef unsigned long   SQLULEN;
    typedef unsigned long   SQLSETPOSIROW;
    ...
  #endif
#else
  typedef long            SQLINTEGER;
  typedef unsigned long   SQLUINTEGER;
  #define SQLLEN          SQLINTEGER
  #define SQLULEN         SQLUINTEGER
  #define SQLSETPOSIROW   SQLUSMALLINT
  ...
#endif

If I understand this correctly it means, for example,  
that -DBUILD_REAL_64_BIT_MODE -DSIZEOF_LONG=8 declares SQLLEN as a long 
which is the same as if neither define is used.

The only define which is different is for SQLSETPOSIROW. That is only used  
in main.cpp:

  SQLSetPos( SQLHSTMT hStmt, SQLSETPOSIROW iRow,
                           SQLUSMALLINT fOption, SQLUSMALLINT fLock )

which calls:

  OdbcStatement::sqlSetPos (SQLUSMALLINT row, 
                           SQLUSMALLINT operation, SQLUSMALLINT lockType)

It looks as if that declaration needs changing. I doubt if that is the cause 
of all your problems, but it certainly indicates that there is still some 
work to do to complete the 64-bit port. Unfortunately I don't think anyone 
is working on this at the moment. If you get to make any progress and want 
to submit a patch I will be happy to apply it.


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

Re: [Firebird-odbc-devel] Problem with special transaction settings

[Paul R. <pr...@ib...>]

On Monday 18 January 2010, Marco Held wrote:
> Hi Paul,
>
> thanks for your reply, but what is the sense at all?! I have to look for
> a solution by myself or will it be fixed soon?
>

I was suggesting that you try running the driver through a debugger to see 
if you can locate the cause of the problem. You are using a transaction 
isolation which is uncommon, so this bug could have been there for a long 
time. 


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

[Firebird-odbc-devel] ODBC driver on 64-bit linux

[Bill G. <bg...@co...>]

I've been trying to build a working ODBC driver on 64-bit linux and, so 
far, have not
been successful. I've basically been following these instructions that
were recently posted to the list:

 >You could (and probably should) build the driver from source.
 >
 >o Check out the code from cvs.
 >(Be sure to use the B2_0_0 tag)
 >
 >o cd to /path/to/checkedoutcode/Builds/Gcc.lin
 >
 >o type at command prompt:
 >make -f makefile.linux all install

I'm using the B2_0_0 tag.
I'm building with gcc 4.1.2.

I made a few changes to makefile.linux (which may have *caused* some
of my problems!):

I added:
ARCH=x86_64

After some debugging, it also appeared that I needed these compiler flags:
-DBUILD_REAL_64_BIT_MODE -DSIZEOF_LONG=8
so I added them.

With the driver built using this approach, simple queries work but
DB operations involving bound parameters are failing. Specifically,
this call in IscStatement::execute()
    if (connection->GDS->_dsql_execute2 (statusVector, &transHandle, 
&statementHandle,
            dialect, inputSqlda, NULL))

is failing with a peculiar server error that leads me to think I have 
some kind of alignment
problem in inputSqlda.

Before continuing my debugging, I just thought I'd see if anyone could 
give me some specific
advice. Can anyone who has successfully built a 64-bit linux driver tell 
me if my addition of
-DBUILD_REAL_64_BIT_MODE -DSIZEOF_LONG=8 is the right thing to do (I do know
that the sizeof(long) with g++ 4.1.2 -m64 is 8, of course)?

Thanks.

Bill

Re: [Firebird-odbc-devel] Problem with special transaction settings

[Marco H. <mh...@de...>]

Hi Paul,

thanks for your reply, but what is the sense at all?! I have to look for a
solution by myself or will it be fixed soon?

Thanks,

Marco Held

phone: +49 271 77202 27
e-mail:  mh...@de...

demig Prozessautomatisierung GmbH – http://www.demig.de – in...@de...
Haardtstraße 40 – D-57076 Siegen – Tel. +49 271 77202 0  –  Fax +49 271
77202 92
Registergericht Siegen HRB 2819 – Geschäftsführer Joachim Herbst, Winfried
Held



-----Ursprüngliche Nachricht-----
Von: Paul Reeves [mailto:pr...@ib...] 
Gesendet: Montag, 11. Januar 2010 11:13
An: fir...@li...
Betreff: Re: [Firebird-odbc-devel] Problem with special transaction settings

On Friday 08 January 2010, Marco Held wrote:
>
> Is this transaction setting not supported?
>

It is most likely you have run into a bug in the driver. Half an hour  
running the code through the debugger might throw some more light on the 
problem.


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

----------------------------------------------------------------------------
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

Re: [Firebird-odbc-devel] Firebird ODBC and MS Excel 2007

[Maya O. (Home) <may...@gm...>]

>
> >>I am trying to connect to my Firebird 1.5 database from Excel 2007.
> >>When I try to add the datasource in to Excel I get the error:
> >>"Unable to obtain list of tables from the data source."
>

Just resolved my own problem. Tried one of the other non-Firebird
datasources, which gave a slightly different error. Googling that error,
found a post that said using "From Microsoft Query" rather than "From Data
Connection Wizard" works for them, and hey presto, it works for me too ;-)

Maya

[Firebird-odbc-devel] Firebird ODBC and MS Excel 2007

[Maya O. (Home) <may...@gm...>]

Hi,

I am trying to connect to my Firebird 1.5 database from Excel 2007.

When I try to add the datasource in to Excel I get the error:

"Unable to obtain list of tables from the data source."

And no connection is made.

If I go to Tools|ODBC in IBExpert, the same ODBC connections work just fine.

I googled the error, but can only find a post by Tim Matsell to this group
in Jan 2007, which I can see no reply to..

Anyone got any ideas?

Thanks
Maya

[Firebird-odbc-devel] SQL_ATTR_ROWS_FETCHED_PTR not work

[<o_v...@vo...>]

Hi,
when use 
SQLSetStmtAttr(hstmt,SQL_ATTR_ROWS_FETCHED_PTR,&NumRowsFetched,0)
to get number of fetched rows after 
SQLFetch(hstmt) or SQLFetchScroll(hstmt,SQL_FETCH_NEXT,0) command

variable (NumRowsFetched) is never changed his value,even so data is
properly readed in buffer.

i test my code also against MSSQL expres and works as i expect, so i
think my code is ok ( i hope:) )

i try SQLExtendedFetch which use function arguments instead of statememt
attribute, and works ok, but for ODBC 3.x apllication it is not recomended
use this function, and is repleaced by SQLFetchScroll, also use SQLExtendedFetch
against MSSQL results to fetching only one row per call(but SQLFetchScroll
works well)

Notes:
i have set ODBC 3 version both in "(windows)ODBC manager" and also on
odbc enviroment handle.
Firebird is version 2.1.3.18185
Firebird_ODBC 2.0.0.148 and 2.0.0.149 (the same result)

[Firebird-odbc-devel] ODBC issue 2.0.0-Win32.exe Duplicating Data

[Grant C. <Gra...@sk...>]

Hi

 

I am very new to Firebird ODBC but here goes

 

We are using Firebird ODBC 2.0.0 Win32.exe on Win XP, Firebird database
1.5 on Win Ser 2003 R2 on a virtual. This is used for the ResPAK
application and configured per the Regedit export, see below for more
detail of configuration but with security attributes removed .

 

When I run a MS Excel 2007 Query using Firebird ODBC 2.0.0 148 against
the Firebird 1.5 database at least 2 of the columns contents duplicate
across unrelated rows. 

 

If I run this same MS Excel 2007 Query with Easysoft 1.03.00.00 then
there is no duplication of column contents to unrelated rows

 

When we run the Firebird ODBC 2.0.0 on an ODBC compliant application
Wherescape Red 5.6.4.0 the same issue occurs with duplicated column
contents. We can reduce the issue to a degree by replacing Nulls and
Blanks in the SQL with a constant character e.g. 'Unknown'. See SQL
below

 

Comments ?

 

Thanks Grant

 

Select CUSTOMER.cust_id

, CUSTOMER.title

, CUSTOMER.fname

, CUSTOMER.lname

, CUSTOMER.phone

, CUSTOMER.mobile

, CUSTOMER.other

, CUSTOMER.rating_r

, CUSTOMER.rating_f

, CUSTOMER.flags

, CUSTOMER.booked

, CUSTOMER.arrived

, CUSTOMER.totalspent

, CUSTOMER.visits

, CUSTOMER.manual_r

, CUSTOMER.manual_f

, NULL

, CUSTOMER.prefsbyarea

, CUSTOMER.lastdate_r

, CUSTOMER.lastdate_f

, CAST(CUSTOMER.LASTTIME as VARCHAR(13))

, CUSTOMER.org_id

, CUSTOMER.dep_id

, CUSTOMER.na_count

, CUSTOMER.na_lastreset

, CUSTOMER.na_total

, CUSTOMER.na_resetby

, CUSTOMER.rna_flag

, CUSTOMER.account_id

, CUSTOMER.phone_idx

, CUSTOMER.mobile_idx

, CUSTOMER.gratuity_level

, CUSTOMER.totalgratuity

, CUSTOMER.manual_grat

, CUSTOMER.vipdiner

, case 

when CUSTOMER.email is null then 'Unknown'  

when CUSTOMER.email = '' then 'blank'

else CUSTOMER.email 

end

, CUSTOMER.totalpoints

, CUSTOMER.privacyflags

, CAST(CUSTOMER.DATE_MODIFIED AS DATE)

, CAST(CUSTOMER.date_created AS DATE)

, NULL

, CUSTOMER.dob_day

, CUSTOMER.dob_month

, CUSTOMER.dob_year

, CUSTOMER.doa_day

, CUSTOMER.doa_month

, CUSTOMER.doa_year

, CUSTOMER.first_visit_date

, CUSTOMER.first_visit_id

, CUSTOMER.cust_lid

, CUSTOMER.f_bookings

, CUSTOMER.f_regular

, CUSTOMER.notes

, CUSTOMER.lname_idx

, CUSTOMER.fname_idx

, CUSTOMER.roomno

, CUSTOMER.res_notes

, CUSTOMER.external_id

>From CUSTOMER WHERE LNAME like 'R%'

; 

 

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\RESPAK_PRD]

"Driver"="C:\\WINDOWS\\system32\\OdbcFb.dll"

"Description"="Respak"

"Dbname"="akspres01:C:\\ResPAKD\\Database\\RESPAK.GDB"

"Client"=""

"Role"=""

"CharacterSet"="NONE"

"JdbcDriver"="IscDbc"

"ReadOnly"="Y"

"NoWait"="Y"

"LockTimeoutWaitTransactions"=""

"Dialect"="3"

"QuotedIdentifier"="Y"

"SensitiveIdentifier"="N"

"AutoQuotedIdentifier"="N"

"UseSchemaIdentifier"="0"

"SafeThread"="Y"

 

Grant Coburn | Senior Datawarehouse Analyst | SKYCITY Auckland Tel +64 9
363 6357 |  Mob +64 21 675 822  |  Fax +64 9 363 6041  | Web
www.skycity.co.nz
<file:///C:\Documents%20and%20Settings\gcoburn\Application%20Data\Micros
oft\Signatures\www.skycity.co.nz>  P Please consider the environment
before printing this e-mail


Attention:This message has been scanned by a reputable SMTP Security Scanner and is believed to be clean, but the sender gives no warranty that it is clean, and excludes any liability for damage caused by unintended attachments. The information contained in this message and/or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender, delete the material from any system and destroy any copies. Nothing in this e-mail designates an information system for the purposes of Section 11(a) of the New Zealand Electronic Transactions Act 2002, unless expressly stated otherwise.

[Firebird-odbc-devel] Firebird in windows 7 ultimate 64 bits

[tom i. <to...@in...>]

Hello,

I install firebird 1.5 (32 bits) on my new Windows 7 ultimate 64 bits. 

I install Firebird ODBC (32 bits and after i test with 64 bits version) and i've : library 'gds32.dll' failed to load 

With firebird 1.56 and ODBC can i use  windows 7 ultimate 64 bits ? If ok how can i do ??

Thanks

Tom


__________ Information from ESET Smart Security, version of virus signature database 4747 (20100106) __________

The message was checked by ESET Smart Security.

http://www.eset.com

Re: [Firebird-odbc-devel] Problem with special transaction settings

[Paul R. <pr...@ib...>]

On Friday 08 January 2010, Marco Held wrote:
>
> Is this transaction setting not supported?
>

It is most likely you have run into a bug in the driver. Half an hour  
running the code through the debugger might throw some more light on the 
problem.


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support