FiveTech Software tech support forums

resulting in a duplicate record in the table The best way to avoid duplicates in a multi-user environment is to use AutoIncrement field. ( FieldType "+" ) Example: Field ID in fwh\samples\customer.dbf While adding a record, we should not assign any value to this AutoInc ...

resulting in a duplicate record in the table The best way to avoid duplicates in a multi-user environment is to use AutoIncrement field. ( FieldType "+" ) Example: Field ID in fwh\samples\customer.dbf While adding a record, we should not assign any value to this AutoInc ...

... "states", nil, { aRow } )endif  But insert not work. Table `states` has 3 fields: id, code, name where id is autoincrement field This should work: oCn:Upsert( "states", nil, { { 0, "KK", "KState" } } ) ...

... } oCn:Upsert( "states", nil, { aRow } ) endif But insert not work. Table `states` has 3 fields: id, code, name where id is autoincrement field This should work: oCn:Upsert( "states", nil, { { 0, "KK", "KState" } } ) ...

... DBF Data using "Fivewin Way" where FIELD "ID" was add FIELD "ID" is used as PRIMARY KEY and work "autoincrement" but METHOD SavePQQ() use currval() AFTER (!) INSERT when APPEND so Fivewin Sample c:\fwh\samples\testpgre.prg FAIL when try to APPEND ...

... it is convenient for him to consolidate tables from different branches into the main table at head quarters. Though I personally prefer using one autoincrement integer field as primary key, when we make FWH library we need to cater to all kinds of programmers and their needs and preferences.

... who wishes to gain control of your application and then try to insert or "Inject" malicious rows into your database .. If you have autoincrement set on your primary key .. there is nothing to stop a malicious attack to insert new rows into your SQL table. If I, on the other hand, ...

does Fivewin use Name "id" as default also for "other" SQL :?: Yes, by default for autoincrement primary field. Programmer can choose different field names. FWH functions allow specifying the structure of a table using a structure like DBSTRUCT(). FWH creates ...

* src/rdd/dbf1.c + added support for autoincrement fields with counter longer then 4 bytes Warning: if someone created tables with such fields i.e. { "I:+", 8, 0 } after my modification which added support for AutoInc flags in all ...

Necesito conocer el ultimo indice (autoincrement) que se le dio a una tabla. Antes lo hacia con GetAutoIncrement y ahora con mariadb? gracias. Saludos, yo lo hago asi, inmediatamente luego del insert cQuery := "SELECT LAST_INSERT_ID() ...

Necesito conocer el ultimo indice (autoincrement) que se le dio a una tabla.
Antes lo hacia con GetAutoIncrement y ahora con mariadb?

gracias.

Saludos colega... Gracias por tu colaboracion. En mi caso, hago un SELECT previo porque alli uso la clausula FOR UPDATE que es la que me va a BLOQUEAR el registro y no permitir que nadie mas accese la tabla al mismo tiempo y pueda duplicarse el valor del consecutivo. Sin embargo, con tu idea puedo a...

Hola, A mi se me ocurre algo sin tener que hacer ningún query previo e incrementar en una variable. No se si entendí tu idea, pero esto debería funcionar: cQuery:="UPDATE TUTABLA SET CAMPO=CAMPO + 1 " // No pongo ningún Where ya que comentas que es solo un registro.  Espero te sirva la ide...

... la colaboracion en sus respuestas. Pero creo que no me explique bien sobre lo que quiero. Lo que me gustaria hacer (si se puede) es que un campo autoincrement se vaya incrementando SIN HACER UN INSERT. Quiero llevar un contador, y por los momentos lo hago asi:       cTabla:= _cPrefijo+'_docventatemp'  ...

Another way is

Code: Select all  Expand view

ALTER TABLE tblname AUTO_INCREMENT = 52;