On 07/25/2011 06:24 PM, Chris Travers wrote:
On Sun, Jul 24, 2011 at 11:53 PM, Sim Zacks wrote:
The goal is to make our system client agnostic, Most of our GUI is written
in wxpython, we also have some web functions and even a barcode terminal
function, written in C#. We would like to use an
Thank you for the reply.
At command line, I ran...
"psql --version"
and received..
"psql (PostgreSQL) 7.5devel"
The database is sitting on a Windows 2003 Server box.
A mapping application, wrote in PHP, runs with Apache 2.05
I know in the past, the project manager would restart the database b
On Tue, Jul 26, 2011 at 7:47 AM, Mcleod, John wrote:
> Thank you for the reply.
>
> At command line, I ran...
> "psql --version"
> and received..
> "psql (PostgreSQL) 7.5devel"
>
> The database is sitting on a Windows 2003 Server box.
> A mapping application, wrote in PHP, runs with Apache 2.05
http://codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/
merlin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, Jul 26, 2011 at 4:41 PM, Merlin Moncure wrote:
> http://codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/
>
> merlin
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-gen
"Mcleod, John" writes:
> Thank you for the reply.
> At command line, I ran...
> "psql --version"
> and received..
> "psql (PostgreSQL) 7.5devel"
Egad. That is an early development snapshot of what eventually got
called the 8.0 release. You should try "select version();" in psql
to verify that
On Tue, Jul 26, 2011 at 1:04 AM, Sim Zacks wrote:
> No need for PL/Mono or any other client specific language. The GUI should be
> dumb, so all I really need to program design is the interface and input
> output methods. When you push a button, it should call the appropriate
> function. The funct
Wondering in their is an ETA on a dmg installer for the mac that does not fail
on Lion?
Best,
-Travis
When I go to "C:\ms4w\apps\pgsql75win\bin" in the command line, and run
"postgres --version", I get the following...
"postgres (PostgreSQL) 7.5devel"
John
-Original Message-
From: Merlin Moncure [mailto:mmonc...@gmail.com]
Sent: Tuesday, July 26, 2011 9:40 AM
To: Mcleod, John
Cc: pgsq
On Mon, Jul 25, 2011 at 5:21 PM, Chris Travers wrote:
> On Mon, Jul 25, 2011 at 12:33 PM, Merlin Moncure wrote:
>
>> exactly. procedural middlewares written in languages like java tend to
>> be bug factories:
>> *) over-(mis-)use of threads
>> *) performance wins moving logic outside the database
Hello,
suppose the following scenario
the car speed is 240
the car has an airbag
Here the first value is integer and the second value is boolean. Consider that
I
have this table structure
feature (feature id feature name)
car (car id, )
car_feature (car id, feature id, value). the val
On 07/26/11 10:02 AM, salah jubeh wrote:
and using ANSI compliant design
American National Standards Institute? they have an ANSI standard on
database schema design or something?
--
john r pierceN 37, W 122
santa cruz ca mid-left coast
Hello John,
I mean ANSI SQL 92 complaint, if I am not mistaken. One solution to this
problem
is to use something like hstore. but it has some disadvantages in my
application so I want another opinion.
Regards
From: John R Pierce
To: pgsql-general@pos
On Jul 26, 2011, at 10:02 AM, salah jubeh wrote:
>
> Hello,
>
> suppose the following scenario
>
> the car speed is 240
> the car has an airbag
>
> Here the first value is integer and the second value is boolean. Consider
> that I have this table structure
>
> feature (feature id feature n
in general, attribute-value sorts of lists are very difficult to use for
relational operations and result in clumsy inefficient queries, as well
as poor data integrity.
whenever possible common attributes shoudl be stored properly as table
fields. reserve EAV for highly sparse freeform inf
Dear all
first of all congratulations on your greak work here since from time to time
i 've found many answers to my problems. unfortunately for this specific
problem i didnt find much relevant information, so i would ask for your
guidance dealing with the following situation:
we have a dedicated
the car speed is 240
the car has an airbag
Here the first value is integer and the second value is boolean. Consider
that I have this table structure
feature (feature id feature name)
car (car id, )
car_feature (car id, feature id, value). the value attribute might have
differen
salah jubeh, 26.07.2011 19:02:
Hello,
suppose the following scenario
the car speed is 240
the car has an airbag
Here the first value is integer and the second value is boolean. Consider that
I have this table structure
feature (feature id feature name)
car (car id, )
car_feature (car i
On Tue, Jul 26, 2011 at 11:06 AM, David Johnston wrote:
> Given “feature” and “car-feature” tables the presence of absence of an entry
> in “car-feature” will accomplish your desire for true/false - i.e., “the car
> has an airbag”. By abstracting just a little every “feature” can be boiled
> dow
-Original Message-
From: Chris Travers [mailto:chris.trav...@gmail.com]
Sent: Tuesday, July 26, 2011 2:32 PM
To: David Johnston
Cc: salah jubeh; pgsql
Subject: Re: [GENERAL] variant column type
> In your example you could create a feature called Top Speed 240kph
>
> If every car is goi
Does anyone have a concise way of doing $SUBJECT?
Best,
Nathan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Copy and paste the column names from the "CREATE TABLE" statement...
You can try using information schema and building a dynamic SQL query inside
a function...
If you let people know WHAT you are trying to accomplish you may find you
get alternative suggestions that you never considered.
SQL i
On Tue, 26 Jul 2011 10:45:27 -0700, John R Pierce wrote:
in general, attribute-value sorts of lists are very difficult to use
for relational operations and result in clumsy inefficient queries,
as
well as poor data integrity.
whenever possible common attributes shoudl be stored properly as
tab
On Tue, Jul 26, 2011 at 2:08 PM, Nathan Boley wrote:
> Does anyone have a concise way of doing $SUBJECT?
select * from foo where (row((foo).*) = row((foo).*)) is null;
merlin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www
On Tue, 26 Jul 2011 17:02:12 +0300, Allan Kamau wrote:
On Tue, Jul 26, 2011 at 4:41 PM, Merlin Moncure
wrote:
http://codesynthesis.com/~boris/blog/2011/07/26/odb-1-5-0-released/
merlin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On 07/26/2011 01:47 PM, Filippos wrote:
we have a dedicated server (8.4.4, redhat) with 24 cpus and 36 GB or RAM. i
would say that the traffic in the server is huge and the cpu utilization is
pretty high too (avg ~ 75% except during the nights when is it much lower).
i am trying to tune the serve
I suggest adding the following parameter to pg_restore:
--rename-table=
When used in conjunction with the --data-only, --schema and -t options (all
three of which would be necessary),
it would allow restoring a table (without indexes) to a different table name
(which would need to already exi
On 07/26/2011 10:02 AM, Allan Kamau wrote:
If the speed is to be measured purely (and simply) on these numbers,
186/12 yields 15.5 (or maybe 16 if your round it up or 15 if you use
integer division). May be about 15~16 times faster would be more in
line with numbers provided.
I guess he did
On Tue, Jul 26, 2011 at 3:48 PM, Michael Nolan wrote:
> I suggest adding the following parameter to pg_restore:
>
> --rename-table=
>
> When used in conjunction with the --data-only, --schema and -t options (all
> three of which would be necessary),
> it would allow restoring a table (without
On Tue, Jul 26, 2011 at 3:53 PM, Greg Smith wrote:
> I guess he did the math on MySQL, too. Could be worse; could have ran into
> http://bugs.mysql.com/bug.php?id=33704 which, as you can see, is totally not
> a bug.
>
Or transactions deadlocking against themselves.
Best Wishes,
Chris Travers
30 matches
Mail list logo
