SELECT LAST_INSERT_ID() as new_id

[sadettinpolat]

Sunucu sürümü: mySQL 5.0.45

test adli ID alanina sahip (autoincremet) bir tabloya veri giriyorum ve hemen akabinde SELECT LAST_INSERT_ID ile yeni ekledigim bu kayida mysql in vermis oldugu ID degerini ogrenmek istiyorum lakin sonuc hep 0 donuyor.

insert into test (DENEME) values ('DENEME');
select LAST_INSERT_ID() as YeniID;
kayit basarili bir sekilde veritabanina eklenmesine ragmen ikinci sorgunun geriye donderdigi deger 0

yanlis yaptigim birsey mi var ?

[ikutluay]

üstad sanırım bu alanda sana yardımcı olacak bir şeyler var. olayın kullanıcı veya bağlantı bazlı olduğundan vs bahsediyor...

http://dev.mysql.com/doc/refman/5.0/en/ ... ue-id.html

ayrıca birde bu olay var. buradan id alanının tipi önemlidir diye anlıyorum ama tam bir çeviri gerekli.

mysql_insert_id() converts the return type of the native MySQL C API function mysql_insert_id() to a type of long (named int in PHP). If your AUTO_INCREMENT column has a column type of BIGINT, the value returned by mysql_insert_id() will be incorrect. Instead, use the internal MySQL SQL function LAST_INSERT_ID() in an SQL query.

For LAST_INSERT_ID(), the most recently generated ID is maintained in the server on a per-connection basis. It is not changed by another client. It is not even changed if you update another AUTO_INCREMENT column with a non-magic value (that is, a value that is not NULL and not 0). Using LAST_INSERT_ID() and AUTO_INCREMENT columns simultaneously from multiple clients is perfectly valid. Each client will receive the last inserted ID for the last statement that client executed.

If you want to use the ID that was generated for one table and insert it into a second table, you can use SQL statements like this:

INSERT INTO foo (auto,text)
VALUES(NULL,'text'); # generate ID by inserting NULL
INSERT INTO foo2 (id,text)
VALUES(LAST_INSERT_ID(),'text'); # use ID in second table

Note that mysql_insert_id() returns the value stored into an AUTO_INCREMENT column, whether that value is automatically generated by storing NULL or 0 or was specified as an explicit value. LAST_INSERT_ID() returns only automatically generated AUTO_INCREMENT values. If you store an explicit value other than NULL or 0, it does not affect the value returned by LAST_INSERT_ID().

For more information on obtaining the last ID in an AUTO_INCREMENT column:

The currently executing statement does not affect the value of LAST_INSERT_ID(). Suppose that you generate an AUTO_INCREMENT value with one statement, and then refer to LAST_INSERT_ID() in a multiple-row INSERT statement that inserts rows into a table with its own AUTO_INCREMENT column. The value of LAST_INSERT_ID() will remain stable in the second statement; its value for the second and later rows is not affected by the earlier row insertions. (However, if you mix references to LAST_INSERT_ID() and LAST_INSERT_ID(expr), the effect is undefined.)

If the previous statement returned an error, the value of LAST_INSERT_ID() is undefined. For transactional tables, if the statement is rolled back due to an error, the value of LAST_INSERT_ID() is left undefined. For manual ROLLBACK, the value of LAST_INSERT_ID() is not restored to that before the transaction; it remains as it was at the point of the ROLLBACK.

Within the body of a stored routine (procedure or function) or a trigger, the value of LAST_INSERT_ID() changes the same way as for statements executed outside the body of these kinds of objects. The effect of a stored routine or trigger upon the value of LAST_INSERT_ID() that is seen by following statements depends on the kind of routine:

*

If a stored procedure executes statements that change the value of LAST_INSERT_ID(), the changed value will be seen by statements that follow the procedure call.
*

For stored functions and triggers that change the value, the value is restored when the function or trigger ends, so following statements will not see a changed value.

The ID that was generated is maintained in the server on a per-connection basis. This means that the value returned by the function to a given client is the first AUTO_INCREMENT value generated for most recent statement affecting an AUTO_INCREMENT column by that client. This value cannot be affected by other clients, even if they generate AUTO_INCREMENT values of their own. This behavior ensures that each client can retrieve its own ID without concern for the activity of other clients, and without the need for locks or transactions.

The value of LAST_INSERT_ID() is not changed if you set the AUTO_INCREMENT column of a row to a non-“magic” value (that is, a value that is not NULL and not 0).

[sadettinpolat]

cevap icin tesekkurler...

mysql consoldan denedigimde sonuc dogru donuyor ama
dbexpress ile sorgulari pespese calistirdigimda sonuc sifir donuyor.

http://bugs.mysql.com/bug.php?id=9481

burda ve birkac yer de daha bu sorundan bahsedilmis. kullandigim mysql surumude bu bugdan etkilenen surumler arasinda geciyor. en iyisi surumu yukseltmek sanirim

[aslangeri]

s.a.
hayırdır kardeş mysql ile ne işin var....

[sadettinpolat]

s.a.
hayırdır kardeş mysql ile ne işin var....

biraz da ona el atalim dedik bakalim nasil birseymis diye

[ikutluay]

başarılar:)

[sadettinpolat]

başarılar:)

saol

[sadettinpolat]

arkadas , neye el atsak birileri hemen satin aliyor.
makinemde trojan falan mi var acep ?

sun , mysqli satin almis