On 10/06/2013 12:37 AM, Willy Raets wrote:
> But the problem is solved (see other post) using a 'SELECT limit 1'
I didn't know about this trick (DELETE LIMIT 1), does this work with
other DBMS, e.g., PostgreSQL? LIMIT is not even standard.
Fernando
-
On Sat, 2013-10-05 at 17:23 +0200, Fernando Martins wrote:
> On 10/05/2013 02:08 PM, Willy Raets wrote:
> >
> > Then adding a primary key should solve that problem.
> >
> Indeed, that is the practical solution, but it is an artificial solution
> because in _theory_ each tuple should represent a un
On 10/05/2013 11:44 PM, Willy Raets wrote:
> On Sat, 2013-10-05 at 10:33 -0400, nando wrote:
>> This isn't really a Gambas issue.
>> The table is poorly created without a primary key with auto-increment.
>> If you wanted to delete one row with values 347 200, then which row would it
>> be?
>> With
On Sat, 2013-10-05 at 10:33 -0400, nando wrote:
> This isn't really a Gambas issue.
> The table is poorly created without a primary key with auto-increment.
> If you wanted to delete one row with values 347 200, then which row would it
> be?
> Without the primary key, you're asking MySQL to guess,
On Sat, 2013-10-05 at 23:11 +0200, Caveat wrote:
> MySQL itself doesn't mind about having no primary key:
>
> mysql> desc test_table;
> +---+-+--+-+-+---+
> | Field| Type| Null | Key | Default | Extra |
> +---+-+--+--
MySQL itself doesn't mind about having no primary key:
mysql> desc test_table;
+---+-+--+-+-+---+
| Field| Type| Null | Key | Default | Extra |
+---+-+--+-+-+---+
| Actual ID | varchar(20) | YES |
On 10/05/2013 02:08 PM, Willy Raets wrote:
>
> Then adding a primary key should solve that problem.
>
Indeed, that is the practical solution, but it is an artificial solution
because in _theory_ each tuple should represent a unique entity. In the
UI, how do you distinguish one record from the oth
r' is in Gambas, MySQL knows nothing of it.
-Nando
-- Original Message ---
From: Willy Raets
To: mailing list for gambas users
Sent: Sat, 05 Oct 2013 14:08:27 +0200
Subject: Re: [Gambas-user] Problem with Gambas and MySql
> On Sat, 2013-10-05 at 10:08 +0200, Fernando Mart
What is the table format?
-- Original Message ---
From: Fernando Martins
To: gambas-user@lists.sourceforge.net
Sent: Sat, 05 Oct 2013 10:08:12 +0200
Subject: Re: [Gambas-user] Problem with Gambas and MySql
> On 10/05/2013 01:25 AM, Willy Raets wrote:
> > On Fri, 2013
On Sat, 2013-10-05 at 10:08 +0200, Fernando Martins wrote:
> On 10/05/2013 01:25 AM, Willy Raets wrote:
> > On Fri, 2013-10-04 at 22:53 +0200, Willy Raets wrote:
> >
> > Nando, Fernando and Caveat,
> >
> > Thanks for your responses.
> >
> >> Content in 'ICzakgewicht' can be like this:
> >> | ID | G
On 10/05/2013 01:25 AM, Willy Raets wrote:
> On Fri, 2013-10-04 at 22:53 +0200, Willy Raets wrote:
>
> Nando, Fernando and Caveat,
>
> Thanks for your responses.
>
>> Content in 'ICzakgewicht' can be like this:
>> | ID | Gewicht |
>> 345 100
>> 345 100
>> 345 50
>> 347 200
>> 347 200
>> 347 200
>>
On Fri, 2013-10-04 at 22:53 +0200, Willy Raets wrote:
Nando, Fernando and Caveat,
Thanks for your responses.
>
> Content in 'ICzakgewicht' can be like this:
> | ID | Gewicht |
> 345 100
> 345 100
> 345 50
> 347 200
> 347 200
> 347 200
> 347 200
@ Fernando and Caveat
Above you can see that mor
Hi Willy
Me again!
Either use LIMIT row_count on your delete statement as per
http://dev.mysql.com/doc/refman/5.0/en/delete.html
Or use an auto-incrementing primary key that your VB clients don't need
to worry about as per
http://dev.mysql.com/doc/refman/5.0/en/example-auto-increment.html
Ki
articular row
-- Original Message ---
From: Willy Raets
To: gambas-user@lists.sourceforge.net
Sent: Fri, 04 Oct 2013 22:53:41 +0200
Subject: [Gambas-user] Problem with Gambas and MySql
> Hi All,
>
> In a bigger project where creating, editing and deleting records wor
Hello Willy
forgive me, I haven't really tried your application, but why can't you
send a SQL DELETE statement?
Fernando
On 10/04/2013 10:53 PM, Willy Raets wrote:
> Hi All,
>
> In a bigger project where creating, editing and deleting records works
> as a charm, only one table is giving me trou
Hi All,
In a bigger project where creating, editing and deleting records works
as a charm, only one table is giving me trouble and just won't delete a
record with reason 'No primary key'.
Now the table in question 'ICzakgewichten' was migrated from an Access
database to MySql and in Access it was
16 matches
Mail list logo