Graeme Geldenhuys wrote:
Very true! Now lets see what they say on the CodeGear newsgroups. :-)
Oh boy - I got them throwing there toys out the cot again. :-) I should
really stop doing that. ;-)
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
On 2009-08-17 01:20, Graeme Geldenhuys wrote:
An exact example would be very helpful. And the old property mapping
to database field doesn't could, because that's a design preference
and such mappings are not always appropriate or possible.
What I have in mind isn't quite an example but I'd
Hi Graeme,
The libpq_api.pas that ships with FPC implements all the functions from the
version 3 native api on windows and linux. This .so/.dll is backwards
compatible even with the latest versions of postgresql server.
I tried TPQConnection in a production environment on a server-side deamon,
Desmond Coertzen wrote:
I tried TPQConnection in a production environment on a server-side
deamon, and bytea was the first missing data type that haunted me. The
encode postgres function will save you here: Encode your bytea field
I can't remember, but I think bytea (I call it blob) work
Jong, I did not make much changes to the fpc files itself. The only change I
made to the api wrapper is the location of the libpq.so / dll file. It use
to load from current working dir, or going on a rampant search according to
the LD_LIBRARY_PATH environment variable on linux. I made a mod where
Hello,
In the past, some people reported problems connecting to the main FPC
website or the main SVN repository. Typical symptoms were empty HTML
pages, but pinging to the server working fine.
The reason for this - which has been given often - was the atypical
window size of the router in front
On 17 Aug 2009, at 17:43, Michael Van Canneyt wrote:
The reason for this - which has been given often - was the atypical
window size of the router in front of the server: Some ISP's routers
or network configuration could not cope with this atypical window
size.
To nitpick: it's not the
On Mon, 17 Aug 2009, Jonas Maebe wrote:
On 17 Aug 2009, at 17:43, Michael Van Canneyt wrote:
The reason for this - which has been given often - was the atypical
window size of the router in front of the server: Some ISP's routers or
network configuration could not cope with this atypical
Op woensdag 22-07-2009 om 00:54 uur [tijdzone +0300], schreef Dimitrios
Chr. Ioannidis:
Hi,
i'm trying to use TBufDataset as a very simple mem dataset but i get a
Stream read error.
I can reproduce it, but first is it legitimate to use TBufDataset like
this ?
Yes, it should work. I
2009/8/16 Michael Van Canneyt mich...@freepascal.org:
However, it's not so spectacular: Attributes are simply old .NET stuff they
ported to Win32. Seems they had to use a workaround through an attribute
class.
Yes you have to create a descendant of TCustomAttribute when you want
to add any
I am not very familiar with the code, so before reporting, I'd like to ask:
trunc\rtl\objpas\classes\writer.inc
procedure TWriter.WriteProperty(Instance: TPersistent; PropInfo: Pointer);
Imagine you a writing an Component, that does have an ancestor.
The same component should have
property
I may have mis-judged t, but the problem is still the same:
when you get to write TPersistenChild you enter the following code
tkClass:
begin
ObjValue := TObject(GetObjectProp(Instance, PropInfo));
if HasAncestor then
begin
AncestorObj :=
12 matches
Mail list logo
