Hi,
Zdravko Balorda wrote:
there are both pg_(un)escape_bytea() functions
but only one pg_escape_string()... I wonder if I may be
missing something here?
Yeah, I think you are. pg_escape_string (funnily enough) escapes string
data which is then stored in the database. You would use this for
Jhonny Velasquez c. schrieb:
hola a todos
Hi,
this is the english mailinglist ... ther's also an spanish mailinglist I
guess ;-)
estoy programando en php
tengo el siguiente esquema de BD
BDACADEMICA
personas(idpersona, nombres, paterno)
BDSIAP
PersonasDatosActualizables(idpersona,
On Tuesday 4. March 2008, li ethan wrote:
>HI guys!
>I've been encounting a problem when I configured PHP to support
>Postgres.I think may be someone in here can solve my problem.
>Postgres version is 8.1.4,and the install path is
> /usr/local/pgsql, PHP is 4.4.2.
>I use this parameter
Glad you found the problem.
On Aug 9, 2006, at 11:42 PM, PostgreSQL Admin wrote:
$connection->execute("SELECT insert_staff_b('$staff
[insert_firstname]'::varchar)");
$connection->execute("SELECT insert_staff_b('".$staff
['insert_firstname']."'::varchar)");
If you are creating SQL functions y
Thanks for the catch. I've tried:
$connection->execute("SELECT
insert_staff_b('$staff[insert_firstname]'::varchar)");
$connection->execute("SELECT
insert_staff_b('".$staff['insert_firstname']."'::varchar)");
None work... I'm scratching my head on this one.
Thanks,
J
On Aug 9, 2006, at 10:36 PM, PostgreSQL Admin wrote:
select insert_staff_b('$_POST['firstname']::varchar)
Still I get this error:
Warning: pg_query(): Query failed: ERROR: function insert_staff_b
(character varying) does not exist HINT: No function matches the
given name and argument types
On Sun, Aug 21, 2005 at 06:35:22AM +0100, Aldor wrote:
> if you want to insert biiig data volumes try either using COPY instead
> of INSERT - it will run much much faster
And if for some reason you have to stick with inserts, group them into
transactions; it will perform much better than individu
Hi, Thank for your answers.
I asked here because I had thought the problem was in
how Postgres manage connections.
Sorry
--- Yasir Malik <[EMAIL PROTECTED]> ha scritto:
> > Hi,
> > I need to connect to 2 differents Postgres 8.0.0
> > databases located in the same machine using the
> same
> > PHP sc
Hi,
On 4/29/05, Mauro Bertoli <[EMAIL PROTECTED]> wrote:
> I need to connect to 2 differents Postgres 8.0.0
> databases located in the same machine using the same
> PHP script with an "db wrapper object" instance
> (pg_Connect)... simply a PHP page with contemporarily
> 2 database connections...
Hi,
I need to connect to 2 differents Postgres 8.0.0
databases located in the same machine using the same
PHP script with an "db wrapper object" instance
(pg_Connect)... simply a PHP page with contemporarily
2 database connections...
I don't think this is the right place to ask this, but there's an
On Apr 21, 2005, at 8:00 AM, Mauro Bertoli wrote:
Hi, I need a PHP wrapper for PostgreSQL...
I found 1000 small "+/- identicals" wrappers but
incompleted
There's an "ufficial" or an suggested PHP wrapper?
Why not use the built-in PHP functions for PostgreSQL? If by wrapper
you mean an abstraction
Thanks Bruno.
I see the potential challenge. If the field value is encrypted, how can
search be done for certain value? Do I have to seach for the encrypted
value? If so, what password or key should I use?
Thanks
"Bruno Wolff III" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On
> If you decrypt the data on the database, the sysadmin can see it.
Hm, you are right. If one does decrypt the data on the database you have to sent the
password to postgresql and so a administrator of the database could easily grasb the
password.
So the only way to go, would be to perform en/d
On Tue, Jul 13, 2004 at 11:35:57 +0200,
Daniel Struck <[EMAIL PROTECTED]> wrote:
> > Keeping the system administrator from seeing the data while making it
> > searchable is difficult. To do this you need to encrypt the data on
> > the client side using a key the client has (and this key has to be
> Keeping the system administrator from seeing the data while making it
> searchable is difficult. To do this you need to encrypt the data on
> the client side using a key the client has (and this key has to be
> protected from loss) and the only searches you can do are equality
> searches using a
On Thu, Jul 08, 2004 at 11:49:36 -0400,
Sarah Tanembaum <[EMAIL PROTECTED]> wrote:
> I was wondering if it is possible to create a secure database system
> usingPostgreSQL/PHP combination?
>
> I have the following in mind:
>
> I wanted to store all my( and my brothers and sisters) important doc
My solution to the problem stated below was to learn plpgsql, and write a
function that loops through the returned records, concatenating a string
together, and returning that string as the Author field.
This function was actually e-mailed to me by a collegue, and I did a bit
of doctoring (it still
Yes, this may be better than foreach()ing through each publication
returned.
But a plpgsql function may suit these needs much better.
On Tue, 27 May 2003, Jean-Luc Lachance wrote:
> KISS
>
> why not use PHP to concatenate the authors while pub_id is the same???
> If you insist on having each au
KISS
why not use PHP to concatenate the authors while pub_id is the same???
If you insist on having each author in its own column,
put them at the end and concatenate with .
jll
Chadwick Rolfs wrote:
>
> So, I have the same problem, but I need all authors for each publication
> to show up in
On Tue, 2003-05-27 at 14:19, Richard Huxton wrote:
> On Tuesday 27 May 2003 5:34 pm, Chadwick Rolfs wrote:
> > So, I have the same problem, but I need all authors for each publication
> > to show up in it's own column. I tried the full join query from a
> > suggestion off pgsql-sql, but it only re
On Tue, 27 May 2003, Richard Huxton wrote:
> On Tuesday 27 May 2003 5:34 pm, Chadwick Rolfs wrote:
> > So, I have the same problem, but I need all authors for each publication
> > to show up in it's own column. I tried the full join query from a
> > suggestion off pgsql-sql, but it only returns O
On Tuesday 27 May 2003 5:34 pm, Chadwick Rolfs wrote:
> So, I have the same problem, but I need all authors for each publication
> to show up in it's own column. I tried the full join query from a
> suggestion off pgsql-sql, but it only returns ONE author id TWICE instead
> of ALL authors at once.
So, I have the same problem, but I need all authors for each publication
to show up in it's own column. I tried the full join query from a
suggestion off pgsql-sql, but it only returns ONE author id TWICE instead
of ALL authors at once.
I'll do some RTFMing of the joins.. and post any results I g
This is caused by the fact that PostgreSQL is case insensitive. In order
for it to actually take the case into account, you need quote your field
names and table names.
So your query would then be: select "NetCode","NetworkName" from
"NetworkTab";
Then you would be able to access the fields wit
Hi,
maybe this problem isn't originated in PEAR, but in pg itself.
Postgres folds everything to lowercase except one within "" (doublequotes).
So, if you - ie.: in psql:
psql=# CREATE TABLE veRYMixedCAse (NetCode integer,...);
then actually you will create a table named 'verymixedcase'.
In
Hi Gurudutt--
Concerning #1, I had a similar problem when porting data from mysql to psql.
I finally ended up just using mysql's COPY command to get the data into
delimited text form, then imported that into psql using its COPY command.
This seems to me to be the easiest way to port over data if
On Wed, May 30, 2001 at 11:14:38PM +0530, Sharmad Naik wrote:
> hi,
> I wanted to know that does postgresql database support php-nuke
This is a php-nuke question. Head to their website and it should be
stated there somewhere.
-Roberto
--
+| http://fslc.usu.edu USU Free
27 matches
Mail list logo
