RE: Help w/ SQL stored procedure

If I am not misunderstanding something obvious... Why not do it the "MaxDB" way? Create a sequence "allocated" for your identity column such as: CREATE SEQUENCE "SEQ_SOMEKEY" INCREMENT BY 1 START WITH 1 MINVALUE 1 MAXVALUE 99 NOCYCLE CA

Re: update...where current of with Python

'Jean-Michel OLTRA' wrote: any additional doc for the SapDB_ResultSet Class ? I can't find neither setFetchSize(), nor cursorName() methods in downloaded MaxDB documentation. True. Until this is fixed, uou can get at the documentation if you have a live SapDB_ResultSet through resultset.cursorName

Re: update...where current of with Python

Le jeudi 29 avril 2004, Dittmar, Daniel a écrit... bonjour, > You have to access the 'inner' cursor object: > cursor = session.cursor () > cursor.execute ('select * from messages') > innerCursor = cursor._Cursor__cursor > # important: read only single rows from the serve

Help w/ SQL stored procedure

I'm not having much luck looking through the MaxDB docs on putting together a simple SQL stored procedure. I was hoping someone might be able to help me with this simple TRIGGER that I'm trying to pull over from a DB2 instance: CREATE TRIGGER WEBTST.F58INSNJDT BEFORE INSERT ON WEBTST.F58NONJ

Re: database instance crashes

Seems that I can't send zip files to the list... The file is not THAT long, so I am sending full: Date Time TID(hex) Typ MsgID LabelMessage-Text ---

Re: database instance crashes

On Thu, Apr 29, 2004 at 11:06:45PM +0300, Andris Spruds wrote: > Hello, > > I have a problem with MaxDB 7.5.00.08. Every few hours the instance goes > down. As I have a few sites running on that instance, I have not been able > to get the exact query/conditions under which the instance crushes. I

database instance crashes

Hello, I have a problem with MaxDB 7.5.00.08. Every few hours the instance goes down. As I have a few sites running on that instance, I have not been able to get the exact query/conditions under which the instance crushes. I would be really grateful for any help or hints on what to do next. I am i

AW: When will simple replication be available with MaxDB 7.5 ?

Hello Jim, what do you understand under the term simple replication? Best Regards, Tilo Heinrich SAP Labs Berlin >-Ursprüngliche Nachricht- >Von: Jim Sanders [mailto:[EMAIL PROTECTED] >Gesendet: Mittwoch, 28. April 2004 15:57 >An: [EMAIL PROTECTED] >Betreff: When will simple replication

R: I cannot reach libSQLDBC.so

Hi Alexander, I've tried with the static lib but I'm getting the same error... Any other suggestion? Hi Alexander, I've re-builded my sourcecode with the following command: gcc -shared -o libMyLib.so -I/home/myUser/sapdb-linux/incl -I/usr/lib/j2sd k1.4.2/include -I/usr/lib/j2sdk1.4.2/include/lin

RE: I cannot reach libSQLDBC.so

Hello Alexio, A look into that SQLDBC package did show me that the linux shared library is missing some essential symbols (and thus will not work). Until we make a more recent SQLDBC package available, your only chance is in using the static library that's also in the package, and apparantly c

RE: kernel error

Hello, if your Redhat 8 uses an enhanced Linux kernel, it could help to use 'export LD_ASSUME_KERNEL=2.2.5' before starting the x_server/database. Then you should check that the user that tries to start the database is member of the database administrator group. This helps to find that group: ca

RE: Multiple share lock one select

Philippe Chaléat wrote: > > Ok. Sorry, my previous mails were not clear enough. > > Here is a concrete case. > > I 've two working sessions, one with transaction 27225 and > one with 27222. > > If I disable dead lock detection and have a look at LOCKS-HOLDER and > LOCK-REQUESTOR, I can see s

Re: R: I cannot reach libSQLDBC.so

Le jeudi 29 avril 2004, Alexio Cassani a écrit... bonjour, > So I've copied the libSQLDBC.so there and then I've run ldconfig, but the > problem persists... You can run your app within `strace -eopen` to trace open() system calls. -- jm -- MaxDB Discussion Mailing List For list arc

Re: loadercli question

Le jeudi 29 avril 2004, Heiko Giesselmann a écrit... bonjour, > The data file t1.dat contains the following entries: > 2004-04-26 07:00:00,1.0,test1 > 2004-04-26 07:00:00,2.0,test2 > 2004-04-26 07:00:00,3.0,test3 > Error during execution > -->-25319 > Missing data for specified column C

Re: Multiple share lock one select - Again (help...)

I'm still looking for info about share lock policy. I found http://lists.mysql.com/maxdb/20666 in which it's said : "Yes, MaxDB keeps some row locks on SELECTs (these 'row_share' locks you may see in LOCKSTATISTICS) if the isolation level requires it. Simply speaking, if you want a 'read commit

R: I cannot reach libSQLDBC.so

> > you have to run 'ldconfig' after copying the libraries to */lib > >henrik > > Hi, in /etc/ld.so.conf is reported the following line: /usr/X11RS/lib So I've copied the libSQLDBC.so there and then I've run ldconfig, but the problem persists... Huh? TIA Alexio -- MaxDB Discussio

loadercli question

Hi, I am having problems with a simple load command. I checked the manuals and I haven't been able to find the probably very basic and simple problem. Table t1 was created using the following statement: CREATE TABLE t1 ( c1 TIMESTAMP, c2 FIXED(10,3), c3 CHAR(255)) I am using a simple loader comm

RE: update...where current of with Python

> Is there a way to specify "WHERE CURRENT OF" for an update statement, > using sapdb.dbapi module > > cursor.execute ("SELECT ... FROM TABLENAME WHERE ... FOR UPDATE OF > COLUMNNAME") > and then ? > cursor.execute ("UPDATE TABLENAME WHERE CURRENT OF ? > > I did not see any kind of getCursorName(

RE: Again ignore trigger after update

Hi, I don't think you can conditionally by-pass firing trigger. But you should be able to achieve similar result by "conditionally" let the trigger does nothing. Here's an example. Let's say I have a CONTROL_TABLE with a single column FLAG If Flag = 0, fire trigger as normal If Flag = 1, no

RE: ODBC? First Row Listed Twice

Hi Don > -Original Message- > From: Don Gray [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 28. April 2004 22:14 > To: [EMAIL PROTECTED] > Subject: ODBC? First Row Listed Twice > > > Anyone experienced the behaviour where the first row in a resultset is > brought back as two rows? We are u

Re: Again ignore trigger after update

Hello, I think that statement inside trigger tr_upd_atab_1 is incorrect: update dba.atab_2 set t2 = t2 + :val2, t3 = t3 + :val3 where t1 = 40 ignore trigger; I have searched for it in documentation but I didn't found "ignore trigger" statement. I think there is no way how to ignore trigger just

Re: Multiple share lock one select

Ok. Sorry, my previous mails were not clear enough. Here is a concrete case. I 've two working sessions, one with transaction 27225 and one with 27222. If I disable dead lock detection and have a look at LOCKS-HOLDER and LOCK-REQUESTOR, I can see something like this : HOLDER TRANSCOUN

update...where current of with Python

bonjour, Is there a way to specify "WHERE CURRENT OF" for an update statement, using sapdb.dbapi module cursor.execute ("SELECT ... FROM TABLENAME WHERE ... FOR UPDATE OF COLUMNNAME") and then ? cursor.execute ("UPDATE TABLENAME WHERE CURRENT OF ? I did not see any kind of getCursorNam