Re: [pgadmin-support] Numeric position
Title: Message In the listview on the main windows, there are 2 values, length and numeric precision. The length is actually the scale in the case of numerics. See http://www.postgresql.org/idocs/index.php?datatype.html#DATATYPE-NUMERIC for more info on numerics. Regards, Dave. -Original Message-From: Willem Luijk [mailto:[EMAIL PROTECTED]] Sent: 28 August 2002 19:42To: [EMAIL PROTECTED]Subject: [pgadmin-support] Numeric position DO you know, when pgadmin talks about the lenght if a numeric is this with or without the fractional part?
Re: [pgadmin-support] SQL Server to Postgres Migration
> -Original Message- > From: Corin Froese [mailto:[EMAIL PROTECTED]] > Sent: 28 August 2002 20:42 > To: [EMAIL PROTECTED] > Subject: [pgadmin-support] SQL Server to Postgres Migration > > > Greetings, > > I've found a problem with the Database Migration Wizard. > When porting SQL Memo fields to Postgres Text fields, hard > returns are replaced with one > of: chr(13), chr(13)||chr(10), or chr(10)||chr(13). > However, when entering new data into a text field, a hard > return is entered as chr(10). > The result of the porting is that the fields or the entire > record is rendered uneditable through ADO code. The records > can be changed with pgAdmin II though. Umm, pgAdmin does it through ADO :-) Seriously though, pgAdmin doesn't edit the data in memo fields in any way, other than to replace \ with \\ and ' with '' just to ensure that a valid SQL query is generated (it does fiddle with dates, times and booleans, just to iron out any regional formatting quirks). The data is selected from the source database into an ADO recordset, which is iterated through, generating an INSERT query for each record which is then executed using ADO again. What can't you edit the data with? Regards, Dave. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-support] [ADMIN] How to execute my trigger when update certain columns
On Wed, 2002-08-14 at 13:09, Raymond Chui wrote: > Let say I have a table has column1 and column2 and I made a trigger for > after INSERT OR UPDATE for each row to execute procedure my_function. > > What I want is the trigger execute my_function only when column1 is > insert or > update, but not going to execute my_function when column2 is insert or > update. The trigger is executed unconditionally, so put the condition inside my_function. If it's an INSERT, column1 must be new, so: IF TG_OP = ''INSERT'' OR (TG_OP = ''UPDATE'' AND (NEW.column1 != OLD.column1 OR (NEW.column1 IS NULL AND OLD.column1 IS NOT NULL) OR (NEW.column1 IS NOT NULL AND OLD.column1 IS NULL) ) ) THEN ... END IF; -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "For yourselves know perfectly that the day of the Lord so cometh as a thief in the night. For when they shall say, Peace and safety; then sudden destruction cometh upon them, as travail upon a woman with child; and they shall not escape." I Thessalonians 5:2,3 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[pgadmin-support] unsubscribe
unsubscribe http://www.ieg.com.br ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[pgadmin-support] unsubscribe
---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
