Re: [GENERAL] Table dependencies

2009-04-14 Thread Kaarel Kitsemets

Thank you.
That worked for me :)

Kaarel

Pavel Stehule wrote:

Hello

no

but, you can search tablename in source code - all stored procedures
store src in pg_proc.prosrc column

regards
Pavel Stehule

2009/4/14 Kaarel Kitsemets :
  

Hi

I need to make a change to a table that many stored procedures depend on. Is
there an automatic way of finding all the functions that depend on a certain
table?
I have tried the dependents and dependencies report in pgAdmin but these do
not include functions.

Thank you in advance,
Kaarel

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general





--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[GENERAL] Table dependencies

2009-04-14 Thread Kaarel Kitsemets

Hi

I need to make a change to a table that many stored procedures depend 
on. Is there an automatic way of finding all the functions that depend 
on a certain table?
I have tried the dependents and dependencies report in pgAdmin but these 
do not include functions.


Thank you in advance,
Kaarel

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[GENERAL] Question about anyelement datatype

2008-11-25 Thread Kaarel

Hi

I need to use the following statement in a stored procedure:

   EXECUTE 'SELECT * FROM ' || v_table_name INTO v_result;

where v_table_name and v_result are the arguments of the function.
v_table_name is of character varying type and v_result is anyelement.


But as I discovered, it's not allowed to write into function arguments. 
I also tried to declare v_result like this:


   v_result v_table_name%ROWTYPE

but that's not allowed either.


Then I tried to use this:

   v_result v_data%TYPE

where v_data is an argument of the same function with anyelement 
datatype, but no luck.



Is there a way to declare such a pseudo-type variable inside the stored 
procedure?


Thank you in advance,
Kaarel

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[GENERAL] PostgreSQL, GnuCash

2004-08-01 Thread Kaarel
Would PostgreSQL be a good enough choise for GnuCash (or Quickbooks or 
the likes) type of program?
What could be the potential drawbacks of using PostgreSQL (perhaps its 
big size)?
What would be a better database for that kind of job?

Kaarel
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
 joining column's datatypes do not match


Re: [GENERAL] Humor me: Postgresql vs. MySql (esp. licensing)

2003-10-09 Thread Kaarel
It's my opinion that we should be using PG, because of the full ACID
support, and the license involved.  A consultant my company hired before
bringing me in is pushing hard for MySql, citing speed and community
support, as well as ACID support.
Does the consultant push "speed AND ACID" or "speed OR ACID"? My point 
is that PostgreSQL is said to be harder to install/maintain/tune than 
MySQL. I have been reading some MySQL mailing list and for what I see 
there, using InnoDB tables (the only way to have foreign keys, 
transactions, and row level locking for MySQL) makes MySQL slower and 
adds complexity to tuning the database. See this thread for example 
http://lists.mysql.com/mysql/148832 . So when someone says that 
PostgreSQL without tuning is 5 times slower than MySQL retrieving the 
same query, it is quite right to also say that MySQL InnoDB without 
tuning is 5 times slower than MySQL MyISAM.

In my opinion you might consider MySQL only when you don't need the 
features provided by PostgreSQL (and even then data consistency and 
durability issues favor PostgreSQL) because if you need them, your 
developers need to implement them and do extra work, spending more time 
and money. It was already mentioned but I'll post this link again 
http://sql-info.de/mysql/ . IMHO if you are not aware of these gotchas 
they can also increase development time because some things are too 
different from regular/logical behavior (or common sense if you will) of 
any other database.

Kaarel

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
   (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])


Re: [GENERAL] About GPL and proprietary software

2003-09-08 Thread Kaarel





  
That "_by whatever means_" seems to include "network link", and that
doesn't sound right.

  
  
Ah, but in order to use it over the network link you need to be
running their server software, on the one side, and their client
access software, on the other.  Both sides are linked to GPL-licensed
software.

Your client software has to link in software belonging to MySQL AB,
and that's where they are now "biting" people on this.

This is one of the reasons why the PHP people removed bundled MySQL
support in version 5 back in June.


Would a perl application using DBI have a similar problem? Or how would
one then legally use PHP with MySQL without GPL-ing your product and
without buying MySQL commercial license?

Kaarel





Re: [GENERAL] About GPL and proprietary software

2003-09-01 Thread Kaarel


This is neither a GNU nor a MySQL mailing list.  I suggest you take
your question to one of those places, as you'll get a better answer.
 

The question in it self was more general than PostgreSQL and MySQL. 
However as I currently need to work with both of them I wanted to make 
clear the actual differences caused by licensing between the two 
products. The other thing is that it is probably a little easier to 
explain and understand if there are concrete examples.

I asked this list because I didn't want to subscribe to yet another list 
for this matter and pgsql-general sure has the competence to answere 
that kind of questions. It has to have.

I asked this list and not MySQL list because I am subscribed to 
mysql-general and comparing the two list content I like more what I see 
in PostgreSQL lists and the concrete example is about PostgreSQL as much 
as it is MySQL. I don't think at a PostgreSQ conference you would guide 
me to MySQL conference when I asked this same question would you?

Licensing is quite difficult to understad (at least for me) yet a very 
important aspect of software development. I don't intend to ruine 
anybodys day I just want a small discussion which in the end would 
explain the cases when the licensing aspect of these two concrete 
products will play an important role in developing software.

Kaarel



---(end of broadcast)---
TIP 8: explain analyze is your friend