> More likely when you deleted the preferences file when trying to
> figure out the display issue you reported I'd wager. There's no reason
> I can see why an upgrade would (or even could) toggle and existing
> setting.
Oh, yeah, that's most certainly possible. Since I deleted that file
several
On Fri, Mar 19, 2010 at 11:12 AM, jus...@magwerks.com
wrote:
>
> The bigger problem is using time stamps to find the record for updating
>
> Timestamps will not be unique as more than 1 record can have the same value
>
> I suggest changing the updating method to use a unique key.
MS-Access achiev
On Fri, Mar 19, 2010 at 6:56 PM, Josh Berkus wrote:
>
>> That behaviour hasn't changed in years. It sounds like you turned on
>> the 'Copy SQL from main for to query tool' option.
>
> I didn't do it manually; somehow it got set to that when I upgraded.
> Thanks for the option, turned off now.
Mor
> That behaviour hasn't changed in years. It sounds like you turned on
> the 'Copy SQL from main for to query tool' option.
I didn't do it manually; somehow it got set to that when I upgraded.
Thanks for the option, turned off now.
--
-- Josh Berkus
On Fri, Mar 19, 2010 at 6:45 PM, Josh Berkus wrote:
> New annoyance for 1.10.1:
>
> 1) connect to a server
> 2) click on a database
> 3) click the "SQL" button to open a new SQL window
> 4) the text of the database definition will be in that SQL window
> 5) use file ... open to open the file you a
New annoyance for 1.10.1:
1) connect to a server
2) click on a database
3) click the "SQL" button to open a new SQL window
4) the text of the database definition will be in that SQL window
5) use file ... open to open the file you actually wanted to edit
6) get prompt "The text has changed. Do yo
Dave,
FWIW, pgAdmin seems to crash for me (1.10.1, OSX 10.5) whenever I let
the query history get too long or open too many busy (15+) query
windows. Since the crash is quite rapid, I haven't been able to
diagnose the exact tipping point. I assume it's probably bad memory
management by xWindows,
The bigger problem is using time stamps to find the record for updating
Timestamps will not be unique as more than 1 record can have the same value
I suggest changing the updating method to use a unique key.
Message from mailto:douglas.lit...@orbitz.com "Little, Douglas"
douglas.lit...@orb
Hi,
We've been struggling with an MS Access 2007 app that updates a PG table. It
was working, and then it wasn't.
It looks like we recreated the table without specifying the precision on the
timestamp columns.
PG is defaulting to timestamp(6), which doesn't work with MS Access. The
finest p
It doesn't crash under Windows, but deleting the join in the canvas does
leave the join in the join tab in the bottom portion. Adding the join back
in the canvas give 2 joins in the bottom portion
On Fri, Mar 19, 2010 at 6:59 AM, Gary Carter
wrote:
> Mac OS X v10.5.8
>
> pgAdmin v1.10.2
>
> 1. Op
On Fri, Mar 19, 2010 at 11:59 AM, Gary Carter
wrote:
> Mac OS X v10.5.8
>
> pgAdmin v1.10.2
>
> 1. Open Query Tool
> 2. select Graphical Query Builder
> 3. drag one table onto canvas, select a column or 2
> 4. drag another table onto canvas, select a column or 2
> 5. drag a join link between the t
Mac OS X v10.5.8
pgAdmin v1.10.2
1. Open Query Tool
2. select Graphical Query Builder
3. drag one table onto canvas, select a column or 2
4. drag another table onto canvas, select a column or 2
5. drag a join link between the tables
6. Click the Join tab at the bottom portion of the dialog
7. Alt
12 matches
Mail list logo
