On Tuesday, 5 September 2017 at 03:22:37 UTC, denizzzka wrote:
On Monday, 4 September 2017 at 17:56:04 UTC, Boris-Barboris
wrote:
On Monday, 4 September 2017 at 16:05:17 UTC, denizzzka wrote:
Sorry fot duplicate answer
Ok, just FYI, I guess what I described was implemented in
libpq for
On Monday, 4 September 2017 at 17:56:04 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 16:05:17 UTC, denizzzka wrote:
Sorry fot duplicate answer
Ok, just FYI, I guess what I described was implemented in libpq
for version 9.6 (but works on any PSQL since 8.4, since they
all
On Monday, 4 September 2017 at 18:37:40 UTC, denizzzka wrote:
On Monday, 4 September 2017 at 15:47:04 UTC, Boris-Barboris
wrote:
On Monday, 4 September 2017 at 15:40:47 UTC, denizzzka wrote:
This is just internal function. Don't try to call it from
your application.
I guess it's the Python
On Monday, 4 September 2017 at 15:47:04 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 15:40:47 UTC, denizzzka wrote:
This is just internal function. Don't try to call it from your
application.
I guess it's the Python curse
Oh... What is it:
PARSE + BIND + EXEC + SYNC
?
Yeah,
On Monday, 4 September 2017 at 17:56:04 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 16:05:17 UTC, denizzzka wrote:
Sorry fot duplicate answer
Ok, just FYI, I guess what I described was implemented in libpq
for version 9.6 (but works on any PSQL since 8.4, since they
all
On Monday, 4 September 2017 at 16:05:17 UTC, denizzzka wrote:
Sorry fot duplicate answer
Ok, just FYI, I guess what I described was implemented in libpq
for version 9.6 (but works on any PSQL since 8.4, since they all
implement extended query protocol i wrote the client for) in a
form of
On Monday, 4 September 2017 at 15:59:47 UTC, denizzzka wrote:
Sorry fot duplicate answer
On Monday, 4 September 2017 at 15:59:47 UTC, denizzzka wrote:
Sorry fot duplicate answer
On Monday, 4 September 2017 at 15:47:04 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 15:40:47 UTC, denizzzka wrote:
This is just internal function. Don't try to call it from your
application.
I guess it's the Python curse
Oh... What is it:
PARSE + BIND + EXEC + SYNC
?
Yeah,
On Monday, 4 September 2017 at 15:53:30 UTC, denizzzka wrote:
I dare say that you are engaged in premature optimization.
Quite possible, but it took tolerable amount of time. I definetly
will play with dpq2 more some day, maybe there is indeed no need
to reinvent libpq. But what's done is
On Monday, 4 September 2017 at 15:47:04 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 15:40:47 UTC, denizzzka wrote:
This is just internal function. Don't try to call it from your
application.
I guess it's the Python curse
Oh... What is it:
PARSE + BIND + EXEC + SYNC
?
Yeah,
On Monday, 4 September 2017 at 15:45:23 UTC, denizzzka wrote:
Also, ORM is typical architecturial error.
https://en.m.wikipedia.org/wiki/Object-relational_impedance_mismatch
It's a tool. Error is when you use wrong tool for your job. ORMs
surely help many people, and do a lot of good.
On Monday, 4 September 2017 at 15:40:47 UTC, denizzzka wrote:
This is just internal function. Don't try to call it from your
application.
I guess it's the Python curse
Oh... What is it:
PARSE + BIND + EXEC + SYNC
?
Yeah, that's what I do currently, just write the whole command
chain (same
On Sunday, 3 September 2017 at 22:57:39 UTC, Boris-Barboris wrote:
If anyone here has some insight on typical architectural errors
wich make ORM writer's life hard, please share.
Also, ORM is typical architecturial error.
https://en.m.wikipedia.org/wiki/Object-relational_impedance_mismatch
On Monday, 4 September 2017 at 15:32:51 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 15:28:11 UTC, denizzzka wrote:
What do you mean?
It seems like a very generic method way to send batched
messages, wich would give a lot of freedom.
This is just internal function. Don't try to
On Monday, 4 September 2017 at 15:28:11 UTC, denizzzka wrote:
What do you mean?
It seems like a very generic method way to send batched messages,
wich would give a lot of freedom.
Possible without any src modify.
Will linux socket get a send called between them, or it will be
buffered by
On Monday, 4 September 2017 at 15:11:37 UTC, Boris-Barboris wrote:
On Monday, 4 September 2017 at 14:42:31 UTC, denizzzka wrote:
https://github.com/denizzzka/vibe.d.db.postgresql uses dpq2
backend
On Monday, 4 September 2017 at 14:42:31 UTC, denizzzka wrote:
https://github.com/denizzzka/vibe.d.db.postgresql uses dpq2
backend
https://github.com/denizzzka/vibe.d.db.postgresql/blob/master/source/vibe/db/postgresql/package.d#L92
Very interesting read, thank you.
Making this:
On Sunday, 3 September 2017 at 22:57:39 UTC, Boris-Barboris wrote:
I tried all existing libraries, and noted pretty mature dpq2
and ddb (and it's hb-ddb fork) libs. I didn't like the first
one, because I didn't want to leave vibe-d eventloop,
https://github.com/denizzzka/vibe.d.db.postgresql
On Monday, 4 September 2017 at 12:07:29 UTC, Jacob Carlborg wrote:
Ah, ok. I didn't know about hb-ddb until you started this
thread. I'm currently one of the maintainers of ddb and I
haven't seen anything upstreamed there.
Haha, yeah, I guess I've developed a habit of looking at github
On Monday, 4 September 2017 at 12:07:29 UTC, Jacob Carlborg wrote:
Ah, ok. I didn't know about hb-ddb until you started this
thread. I'm currently one of the maintainers of ddb and I
haven't seen anything upstreamed there.
Me too...
/P
On 2017-09-04 10:12, Boris-Barboris wrote:
On Monday, 4 September 2017 at 06:40:09 UTC, Jacob Carlborg wrote:
If would be great if you want to upstream your improvements.
I think it's a bit unfortunate that everyone is rolling their own
implementations in this community instead of working
On Monday, 4 September 2017 at 09:30:06 UTC, Suliman wrote:
Could you give an example how to make connection object if I
need access to it from several classes? Should it be global?
"""Good way""" is probably to wrap it into some ConnectionPool
(at least that's what I did).
Snipper from
Could you give an example how to make connection object if I need
access to it from several classes? Should it be global?
On Monday, 4 September 2017 at 06:40:09 UTC, Jacob Carlborg wrote:
If would be great if you want to upstream your improvements.
I think it's a bit unfortunate that everyone is rolling their
own implementations in this community instead of working
together. I would say that it's rare to need
On 2017-09-04 00:57, Boris-Barboris wrote:
I tried all existing libraries, and noted pretty mature dpq2 and
ddb (and it's hb-ddb fork) libs. I didn't like the first one, because I
didn't want to leave vibe-d eventloop, and the second one was native
(big plus for me), supported vibe-d sockets.
Hi! Couple of weeks ago I was approached with a task of writing
simple microservice, and I decided to give D a chance. The
problem with performance became apparent very soon, and I started
to look for the cause. I tried all existing libraries, and noted
pretty mature dpq2 and ddb (and it's
27 matches
Mail list logo
