On Sun, 20 Nov 2016 00:33:23 +0100 (CET)
Michael Van Canneyt wrote:
>[...]
> It depends. MySQL 5.7 is supported in the mysql57dyn.pp unit, but I am not
> sure it is included in Lazarus 1.6.
It is shipped with fpc 3.0.0, so yes.
Mattias
___
fpc-pascal
On Sat, 19 Nov 2016, Lars wrote:
On Sat, November 19, 2016 12:05 pm, Terry A. Haimann wrote:
Is it possible to connect to MySQL 5.7 using TSQLConnection or will I
have to downgrade my MySQL Version? I have FreePascal 3.0.0 which appears
to be the most current version. I have it on a Ubuntu
On Sat, November 19, 2016 12:05 pm, Terry A. Haimann wrote:
> Is it possible to connect to MySQL 5.7 using TSQLConnection or will I
> have to downgrade my MySQL Version? I have FreePascal 3.0.0 which appears
> to be the most current version. I have it on a Ubuntu Linux 16.10 X86-64
> system.
Is it possible to connect to MySQL 5.7 using TSQLConnection or will I
have to downgrade my MySQL Version? I have FreePascal 3.0.0 which
appears to be the most current version. I have it on a Ubuntu Linux
16.10 X86-64 system.
___
fpc-pascal maillist -
Hi,
I'm using TMySQL50Connection and TSQLQuery to do a query on a mysql server. Is
there a way that you can set a timeout on a query so that it also automatically
kills the mysql process after the timeout and doesn't keep loading the mysql
server?
Thanks,
Tom
Now have proper version of MySQL on machine
Thank you all for help. Compiles and mostly runs :)
On 2009-10-16, at 9:21 AM, Jonas Maebe wrote:
On 16 Oct 2009, at 15:12, Paul Davidson wrote:
Ok, 32 bit universal it is!
Is there any database access method that works with this mode for
10
On 16 Oct 2009, at 15:12, Paul Davidson wrote:
Ok, 32 bit universal it is!
Is there any database access method that works with this mode for
10.6.1? And how?
Since MySQL is not shipped with Mac OS X, you somehow installed/
obtained an x86_64 version of its client library. Install/obtain
Ok, 32 bit universal it is!
Is there any database access method that works with this mode for
10.6.1? And how?
Again, thank you
On 2009-10-16, at 8:59 AM, Jonas Maebe wrote:
On 16 Oct 2009, at 14:51, Vincent Snijders wrote:
Jonas Maebe schreef:
That's correct, FPC 2.2.4 only support
On 16 Oct 2009, at 14:51, Vincent Snijders wrote:
Jonas Maebe schreef:
That's correct, FPC 2.2.4 only support i386 and PowerPC for Mac OS
X. The upcoming 2.4.0 release will also support x86_64, PowerPC/64
and ARM.
As far as I could see, there are no x86_64 Mac OS X snapshots. Is
that co
Jonas Maebe schreef:
That's correct, FPC 2.2.4 only support i386 and PowerPC for Mac OS X.
The upcoming 2.4.0 release will also support x86_64, PowerPC/64 and ARM.
As far as I could see, there are no x86_64 Mac OS X snapshots. Is that correct?
Vincent
On 16 Oct 2009, at 14:16, Paul Davidson wrote:
dsl-corax:~ pauldavidson$ lipo -info /Users/pauldavidson/dev/cape96/
libmysqlclient.a
input file /Users/pauldavidson/dev/cape96/libmysqlclient.a is not a
fat file
Non-fat file: /Users/pauldavidson/dev/cape96/libmysqlclient.a is
architecture: x8
dsl-corax:~ pauldavidson$ lipo -info /Users/pauldavidson/dev/cape96/
libmysqlclient.a
input file /Users/pauldavidson/dev/cape96/libmysqlclient.a is not a
fat file
Non-fat file: /Users/pauldavidson/dev/cape96/libmysqlclient.a is
architecture: x86_64
Noted that Xcode is set for 32 bit univers
On 15 Oct 2009, at 18:02, Paul Davidson wrote:
Some linker output:
ld: warning: in /Users/pauldavidson/dev/cape96/libmysqlclient.a,
file is not of required architecture
Undefined symbols:
[snip]
It goes on...
Do note the 'file is not of required architecture'. Ummm
It means that th
Here is the head of the unit:
{
cMySQL.pas
cape61
Created by Paul Davidson on 2005/01/18.
Copyright (c) 2005 Corax Networks.Inc.. All rights reserved.
}
unit cMySQL;
{$I Directives.inc}
interface
{$linklib libmysqlclient.a}
uses
cBase,
cKey,
cStack,
mysql4;
On 15 Oct 2009, at 16:03, Paul Davidson wrote:
On 2009-10-15, at 7:13 AM, Jonas Maebe wrote:
On 14 Oct 2009, at 18:14, Paul Davidson wrote:
FPC 2.2.4
OS X 10.6.1
Xcode 3.2
All references to MySQL function are unresolved by linker.
libMySQLclient.a is copied to .pas directory. Using FP
Added libmysqlclient.a to the project and it gets automatically
included in Tagets/cape96/Link Binary With Libraries. Again same
linker errors: Symbols not found. Also tried libmysqlclient.la. Same
result.
When looking at examples and tests in FPC for MySQL they do not
contain any refe
On 14 Oct 2009, at 18:14, Paul Davidson wrote:
FPC 2.2.4
OS X 10.6.1
Xcode 3.2
All references to MySQL function are unresolved by linker.
libMySQLclient.a is copied to .pas directory. Using FPC test code
for MySQL as template.
When you use Xcode, you have to use the Xcode way to link
FPC 2.2.4
OS X 10.6.1
Xcode 3.2
All references to MySQL function are unresolved by linker.
libMySQLclient.a is copied to .pas directory. Using FPC test code for
MySQL as template.
Any hints please?
___
fpc-pascal maillist - fpc-pascal@lists.f
On Fri, 15 Feb 2008, wrote:
> Try this:
>
> q.SQL.Clear;
> q.Add('LOAD DATA INFILE ''data.txt'' INTO TABLE database.my_table;');
> q.Execute; // <-- I don't remember the correct command right now
>
Normally it is:
Q.ExecSQL;
Michael.
___
fpc-pa
Try this:
q.SQL.Clear;
q.Add('LOAD DATA INFILE ''data.txt'' INTO TABLE database.my_table;');
q.Execute; // <-- I don't remember the correct command right now
Leonardo
--- Wolfram Kläger <[EMAIL PROTECTED]> wrote:
> Ok. First one was simple. Keyword and opening bracket must be separated
> by a
Ok. First one was simple. Keyword and opening bracket must be separated
by a blank, e.g.
'.. MYTABLE(..' // wrong
'.. MYTABLE (..' // great
'..)values(..' // wrong
'..) values (..' // great
All field contents have to be bracketed by double apostrophes, e.g.
q.sql.add('''Florian Klaempfl'',')
Along Joost's examples I managed to get connected, create a table, put a
query, get the result, and insert a single row. But when I try to insert
several rows at once, I get an EDatabaseError "near" to first char of
second row.
...
q.SQL.Clear;
q.Add('insert into MYTABLE(c1, c2, ..) values ');
q.A
baron kractor wrote:
Well, I'm extremely new to this sort of thing, and there's no comments in
the example code. Some of the stuff I'm able to puzzle through but some of
it isn't making much sense at all.
Feel free to ask it :)
___
fpc-pascal maillist -
lorian Klaempfl
Sent: November 24, 2003 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: [fpc-pascal]mysql unit under win32
baron kractor wrote:
> Was just curious is anyone had come across any worthy documentation /
> examples of using the mysql unit in a win32 environment?
Hmm, it's use is
baron kractor wrote:
Was just curious is anyone had come across any worthy documentation /
examples of using the mysql unit in a win32 environment?
Hmm, it's use is straight forward, no? Where are the problems?
___
fpc-pascal maillist - [EMAIL PROTE
Was just curious is anyone had come across any worthy documentation /
examples of using the mysql unit in a win32 environment?
___
fpc-pascal maillist - [EMAIL PROTECTED]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
IIRC, besides adding new data fields, they even changed the field order
(!) in their communication structs between minor versions like from 3.22
to 3.23 - breaking the fpc mysql units every couple of month. Not very
programmer friendly...
Rainer Hantsch wrote:
But why not include at least two m
On Tue, 7 Oct 2003, Michael Van Canneyt wrote:
| No, because the distribution will only contain 1 version.
| Not all people install sources.
|
| Michael.
Yes, that's what I also do. I use only FreePascal without all the sources and
classes.
But why not include at least two mysql units to the dist
On Tue, 7 Oct 2003, Rainer Hantsch wrote:
> Hi!
>
> I did not program very much with MySQL in FPC until now, but when I understand
> right, there are currently only three different MySQL unit versions.
> One is very old, one is valit up to 3.2, and then there is one for v4.0.
>
> Why not handle
Hi!
I did not program very much with MySQL in FPC until now, but when I understand
right, there are currently only three different MySQL unit versions.
One is very old, one is valit up to 3.2, and then there is one for v4.0.
Why not handle minor differences within one and the same unit and use
di
On Mon, 6 Oct 2003, Florian Klaempfl wrote:
> Michael Van Canneyt wrote:
> >
> > On Mon, 6 Oct 2003, Johann Glaser wrote:
> >
> >
> >>Hi!
> >>
> >>
> >>>They are available in source form only, not in binary form.
> >>
> >>Ah, I see. That is why they are not in my .debs.
> >>
> >>Why aren't they
Michael Van Canneyt wrote:
On Mon, 6 Oct 2003, Johann Glaser wrote:
Hi!
They are available in source form only, not in binary form.
Ah, I see. That is why they are not in my .debs.
Why aren't they distributed in compiled form too?
Because they have the same name as the 3.23 files. You can on
On Mon, 6 Oct 2003, Johann Glaser wrote:
> Hi!
>
> > They are available in source form only, not in binary form.
>
> Ah, I see. That is why they are not in my .debs.
>
> Why aren't they distributed in compiled form too?
Because they have the same name as the 3.23 files. You can only have 1
bina
Hi!
> They are available in source form only, not in binary form.
Ah, I see. That is why they are not in my .debs.
Why aren't they distributed in compiled form too?
Bye
Hansi
--
Johann Glaser <[EMAIL PROTECTED]>
Vienna University of Technology
Electrical Engineering
http:/
On Mon, 6 Oct 2003, Johann Glaser wrote:
> Hi!
>
> > > Since then I updated to FPC 1.0.10. This doesn't bring these files any
> > > more.
> >
> > It does. I didn't test the source package, but the CVS repository
> > definitely contains the 4.0 units.
>
> Seems that they are forgotten in the fp-u
Hi!
> > Since then I updated to FPC 1.0.10. This doesn't bring these files any
> > more.
>
> It does. I didn't test the source package, but the CVS repository
> definitely contains the 4.0 units.
Seems that they are forgotten in the fp-units-db Debian package.
Is it intended that the MySQL 4.0
On Mon, 6 Oct 2003, Johann Glaser wrote:
> Hi!
>
> Some months ago I developed a program using MySQL as backend database.
> This was MySQL 4.0 and therefore I used the MySQL 4.0 units. They have
> been stored in /usr/lib/fpc/1.0.6/units/linux/mysql/ver40/. This was
> with FPC 1.0.6.
>
> Since th
Hi!
Some months ago I developed a program using MySQL as backend database.
This was MySQL 4.0 and therefore I used the MySQL 4.0 units. They have
been stored in /usr/lib/fpc/1.0.6/units/linux/mysql/ver40/. This was
with FPC 1.0.6.
Since then I updated to FPC 1.0.10. This doesn't bring these files
hi,
I've a problem with the mysql_data_seek procedure with fpc 1.0.10.
If I call this function in the main program block it runs correctly but
if I call this one into a function or procedure this moves the row
pointer to nil, except if all the procedures or functions that call
mysql_data_seek u
Thanks - I've got that installed already.
g.
On Tue, 11 Feb 2003, Anton Tichawa wrote:
> On Monday 10 February 2003 19:47, you wrote:
> > Can someone point me to some example code that shows access to MySQL via
>
> http://www.freepascal.org/contrib/db.php3?category=Database
>
> --
>
> -
On Monday 10 February 2003 19:47, you wrote:
> Can someone point me to some example code that shows access to MySQL via
http://www.freepascal.org/contrib/db.php3?category=Database
--
--
"Adas Methode war, wie sich zeigen wird, Tagträume in offenbar korrekte
Berechnungen einzuweben."
On Mon, 10 Feb 2003, Preben Mikael Bohn wrote:
> Hi Gene, have a look at http://www.freepascal.org/packages/mysql.html
>
> It should be included in your FPC, I think...
>
> Best regards Preben
>
That's a great example of reading, now I need a snippet that shows a write
operation. Ideas?
tnx.
Hi Gene, have a look at http://www.freepascal.org/packages/mysql.html
It should be included in your FPC, I think...
Best regards Preben
Gene Buckle mumbled something about:
> Can someone point me to some example code that shows access to MySQL via
> FPC?
>
> tnx.
>
> g.
>
>
>
>
Can someone point me to some example code that shows access to MySQL via
FPC?
tnx.
g.
___
fpc-pascal maillist - [EMAIL PROTECTED]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
44 matches
Mail list logo