Search the Gambas Mailinglists

... is the faulty query, and the corrected one, I mention in the thread: > > > --=|Set the inherits key in Classes. (Faulty)|=-- > > UPDATE wk_classes > SET inherits_id = > ( > SELECT A.id > FROM wk_classes AS A > WHERE A.name = wk_classes.inherits_name > ) > ; > --=|Set the inherits key in...

... is false to start but seems to try and create a unique name >> >> When set to true it appears to create a non unique name. >> >> And as far as a unique name goes, it must start with a : for the system >> to recognize it as unique... >...

... it is possible to close the dialog and have both printer.file > >> and printer.name set. > >> > >> === correction === > >> it is bugged. > >> I made a simple ... where setup() is called and just after return > >> the values of .file and .name are printed. It is so easy to get them > >> both set... > >> > >> -- BUT...

... is false to start but seems to try and create a unique name >>> >>> When set to true it appears to create a non unique name. >>> >>> And as far as a unique name goes, it must start with a : for the system >>> to recognize it as unique......

... set GB[%s] mysql[%s]\n", > > > GB.System.Charset(), mysql_character_set_name(conn)); >>> > > > before and after string > > > <<< set_character_set(db); >>>. > > > Compiled only this driver, copied it to /usr/lib/gambas2. Run my > > > program. Result: > > > <<< Character set GB[UTF-8] mysql[latin1] > > > Character set GB[UTF-8] mysql[latin1] >>> > >...

... way, postgresql "doesn't really care" whether the table has a primary key set or not. Nor does it care whether a delete or an update query uses a unique row ... it? Well, not at all really. It relies on the WHERE clause to identify the set of rows to be operated on and that is all. If such a clause identifies...

... Under postgresql > it is the execution of one SQL command: > UPDATE horse SET name='Cherry Zontop', namechanged=TRUE, oldname='Lemon > Liniment' WHERE name='Lemon Liniment'; > > * I have simplified the story a fair bit, there are around 18 underlying > tables that have the horse name as the foreign key or as part of the > foreign key. > > postgres, because it...

... Either I missed it, either > it's a PolicyKit thing. > Anyway, you can set the DBus.Name property before doing any other DBus call, to choose the name you want. Regards, -- Benoît Minisini Previous message (by thread): [Gambas-user] Dbus unique name seems incorrect Next message (by thread): [Gambas-user] Dbus unique name...

... Either I missed it, either >> it's a PolicyKit thing. >> > > Anyway, you can set the DBus.Name property before doing any other DBus > call, to choose the name you want. > > Regards, > > -- > Benoît Minisini > > ----[ ... ]---- Previous message (by thread): [Gambas-user] Dbus unique name seems incorrect Next message (by thread): [Gambas-user] Dbus unique name...

... Under postgresql > it is the execution of one SQL command: > UPDATE horse SET name='Cherry Zontop', namechanged=TRUE, oldname='Lemon > Liniment' WHERE name='Lemon Liniment'; > > * I have simplified the story a fair bit, there are around 18 underlying > tables that have the horse name as the foreign key or as part of the > foreign key. > > postgres, because it...