On Tue, 3 Jul 2007, Joost van der Sluis wrote:
> On Tue, 2007-07-03 at 17:38 +0200, Michael Van Canneyt wrote:
> > > What I do like is the idea of storing strings in a
> > > widestring/ansistring. I tried to implement that earlier, but it's
> > not
> > > doable in a Delphi-compatible way. As you
On Tue, 2007-07-03 at 17:38 +0200, Michael Van Canneyt wrote:
> > What I do like is the idea of storing strings in a
> > widestring/ansistring. I tried to implement that earlier, but it's
> not
> > doable in a Delphi-compatible way. As you said, you don't have that
> > problem. But it's still somet
On Tue, 3 Jul 2007, Joost van der Sluis wrote:
> On Tue, 2007-07-03 at 14:13 +0200, Martin Schreiber wrote:
> > > I aggree with Michael on this. Besides, last time I looked at your
> > > 'TBufDataset' (which is a actually a fork, offcourse) it only
> > > implemented blob-fields, on top of the ex
On Tue, 2007-07-03 at 14:13 +0200, Martin Schreiber wrote:
> > I aggree with Michael on this. Besides, last time I looked at your
> > 'TBufDataset' (which is a actually a fork, offcourse) it only
> > implemented blob-fields, on top of the existing TBufDataset.
> >
> > The current TBufDataset also s
Joost van der Sluis wrote:
When I set ParseSQL to False, the object inspector in Lazarus says
"updating is only possible if ParseSQL is true" - unless I make it
readonly, which defeats the purpose.
That's a but, I think. It should check if there are any
update/delete/insert
On Tue, 3 Jul 2007, Martin Schreiber wrote:
> On Tuesday 03 July 2007 14.49, Michael Van Canneyt wrote:
> >
> > Quick question, before I continue with the evaluation:
> >
> > I find no evidence of this last thing in the code ? (in trunk, that is)
> > msbufdataset has fixed buffers for strings, a
On Tuesday 03 July 2007 14.49, Michael Van Canneyt wrote:
>
> Quick question, before I continue with the evaluation:
>
> I find no evidence of this last thing in the code ? (in trunk, that is)
> msbufdataset has fixed buffers for strings, and uses 1 byte per char.
>
There is some garbage in the dir
On Tue, 3 Jul 2007, Martin Schreiber wrote:
> On Tuesday 03 July 2007 13.16, Joost van der Sluis wrote:
> > On Tue, 2007-07-03 at 12:57 +0200, Michael Van Canneyt wrote:
> > > I'd rather see that the whole is coordinated a bit. I don't think all
> > > this
> > > duplication is a good idea; One s
On Tue, 3 Jul 2007, Martin Schreiber wrote:
> On Tuesday 03 July 2007 12.57, Michael Van Canneyt wrote:
> > I'd rather see that the whole is coordinated a bit. I don't think all this
> > duplication is a good idea; One solid set of components makes much more
> > sense: the number of developers a
On Tuesday 03 July 2007 13.16, Joost van der Sluis wrote:
> On Tue, 2007-07-03 at 12:57 +0200, Michael Van Canneyt wrote:
> > I'd rather see that the whole is coordinated a bit. I don't think all
> > this
> > duplication is a good idea; One solid set of components makes much
> > more
> > sense: the
On Tuesday 03 July 2007 12.57, Michael Van Canneyt wrote:
> I'd rather see that the whole is coordinated a bit. I don't think all this
> duplication is a good idea; One solid set of components makes much more
> sense: the number of developers available for it's maintenance would
> double. The end u
On Tue, 2007-07-03 at 12:57 +0200, Michael Van Canneyt wrote:
>
> I'd rather see that the whole is coordinated a bit. I don't think all
> this
> duplication is a good idea; One solid set of components makes much
> more
> sense: the number of developers available for it's maintenance would
> double
On Tue, 2007-07-03 at 20:30 +1000, John wrote:
> > > 1) When I tried editing in a dbGrid, I had trouble with the field
> > > length. Looking through the code, I can't see anywhere where the length
> > > of a string is checked against the length of the field, and longer
> > > strings appear to
Joost van der Sluis wrote:
On Tue, 2007-07-03 at 17:55 +1000, John wrote:
I have a basic editable connection working now, but there remain a
number of questions:
1) When I tried editing in a dbGrid, I had trouble with the field
length. Looking through the code, I can't see any
Michael Van Canneyt wrote:
I'd rather see that the whole is coordinated a bit. I don't think all this
duplication is a good idea; One solid set of components makes much more
sense: the number of developers available for it's maintenance would double.
The end user would also benefit, as we can gi
On Tue, 3 Jul 2007, Martin Schreiber wrote:
> On Tuesday 03 July 2007 11.36, Michael Van Canneyt wrote:
> >
> > Why don't you contribute the database code to the FCL ? This way, everybody
> > benefits from it. It's non-visual code, so it can perfectly be separated
> > out.
> >
> It depends on th
On Tuesday 03 July 2007 11.36, Michael Van Canneyt wrote:
>
> Why don't you contribute the database code to the FCL ? This way, everybody
> benefits from it. It's non-visual code, so it can perfectly be separated
> out.
>
It depends on the completely rewritten tmsebufdataset, if you want to use the
On Tue, 2007-07-03 at 17:55 +1000, John wrote:
> I have a basic editable connection working now, but there remain a
> number of questions:
>
> 1) When I tried editing in a dbGrid, I had trouble with the field
> length. Looking through the code, I can't see anywhere where the length
> of a str
On Tue, 3 Jul 2007, Martin Schreiber wrote:
> On Tuesday 03 July 2007 09.55, John wrote:
> > I have a basic editable connection working now, but there remain a
> > number of questions:
> >
> Have a look on MSEide+MSEgui:
>
> http://www.homepage.bluewin.ch/msegui/
>
> Screenshots:
> http://sour
On Tuesday 03 July 2007 09.55, John wrote:
> I have a basic editable connection working now, but there remain a
> number of questions:
>
Have a look on MSEide+MSEgui:
http://www.homepage.bluewin.ch/msegui/
Screenshots:
http://sourceforge.net/project/screenshots.php?group_id=165409
It has lookup
I have a basic editable connection working now, but there remain a
number of questions:
1) When I tried editing in a dbGrid, I had trouble with the field
length. Looking through the code, I can't see anywhere where the length
of a string is checked against the length of the field, and longer
On Fri, 2007-06-29 at 18:35 +1000, John & Marg Sunderland wrote:
> Following earlier advice, I constructed a simple query ("select * from
> organiser.durn_type"), set readonly to false and tried to modify some
> data and commit it.
>
> (At this point I should note that I am doing this from Laza
Following earlier advice, I constructed a simple query ("select * from
organiser.durn_type"), set readonly to false and tried to modify some
data and commit it.
(At this point I should note that I am doing this from Lazarus 0.9.22
with the supplied fpc, 2.0.4 I think, and I am connecting to a
On Fri, 2007-06-22 at 10:43 +1000, John wrote:
> Joost van der Sluis wrote:
>
> > IN principle you can set ReadOnly to false and ParseSQL to true. That
> > way sqldb tries to parse your query. If it's a simple 'select * from
> > table' the TSQLQuery will be updateable. It automatically generates
>
Joost van der Sluis wrote:
IN principle you can set ReadOnly to false and ParseSQL to true. That
way sqldb tries to parse your query. If it's a simple 'select * from
table' the TSQLQuery will be updateable. It automatically generates
update/delete and insert queries. For the 'where' clause is us
Henry Vermaak wrote:
On 20/06/07, Joost van der Sluis <[EMAIL PROTECTED]> wrote:
You mean how many rows are affected by the last query you've run? I saw
request for that earlier.
But imho, you never need it. You always should know how many rows are
affected before you execute a query.
Of cou
On 20/06/07, Joost van der Sluis <[EMAIL PROTECTED]> wrote:
You mean how many rows are affected by the last query you've run? I saw
request for that earlier.
But imho, you never need it. You always should know how many rows are
affected before you execute a query. It could be a debug-tool,
thou
Joost van der Sluis wrote:
- please send me some hints to configure a query as fast as possible --
read only and unidirectional. I will open the query, read everything and
close it.
Set ParseSQL to false. (This wil automatically set readonly to true) It
won't be unidirectional, but I made an
On Wed, 2007-06-20 at 14:43 -0300, Joao Morais wrote:
> Joost van der Sluis wrote:
>
> > Those are the basics. If you have questions, ask them here.
>
> I have two!
>
> - please send me some hints to configure a query as fast as possible --
> read only and unidirectional. I will open the query,
Joost van der Sluis wrote:
Those are the basics. If you have questions, ask them here.
I have two!
- please send me some hints to configure a query as fast as possible --
read only and unidirectional. I will open the query, read everything and
close it.
- what about RowsAffected?
Thanks!
On Wed, 2007-06-20 at 22:32 +1000, John wrote:
> Is there any documentation for the SQLDB components ? I have put a fair
> bit of effort in to looking round the FPC and Lazarus documentation and
> wiki areas, and while there are a few helpful hints here and there, I
> have not been able to find a
Is there any documentation for the SQLDB components ? I have put a fair
bit of effort in to looking round the FPC and Lazarus documentation and
wiki areas, and while there are a few helpful hints here and there, I
have not been able to find any sort of overview of how the components
are suppose
32 matches
Mail list logo
