In Pharo 3.0 there was a Add/Remove breakpoint (experimental) method popup
menu option. I do not see this capability in version 4.0. Is this feature
still available or has it been removed? If still available, then how does
one get it instantiated?
Brad Selfridge
-
Brad Selfridge
--
View
Steph,
I completely agree. This type of hyperbole makes the casual observer think
that the Smalltalk community can come off as petty. We're better than this.
We should ALL have the goal of promoting Smalltalk. I know that a lot of you
have and I applaud all of you for your efforts. The more the m
The "libmysqlclient18:amd64" looks suspicious.
brad@brads-linux-laptop:~$ sudo dpkg -l | grep mysql | awk ' { print $2 } '
libdbd-mysql-perl
libmysqlclient18:amd64
libmysqlclient18:i386
libmysqlcppconn7
libopendbx1-mysql
libqt4-sql-mysql:i386
mysql-client
mysql-client-5.5
mysql-client-core-5.5
m
My database is 64 bit on my 64bit Ubuntu machine.
However, on my 32bit Ubuntu 14.04 machine, I have a 64 debian VM running
that has a 64bit MySQL running which I can access just fine from 32bit host
machine running Pharo.
-
Brad Selfridge
--
View this message in context:
http://forum.worl
Ill have to check
Brad Selfridge
913-269-2385
> On Nov 17, 2014, at 9:41 AM, Stephan Eggermont [via Smalltalk]
> wrote:
>
> Hi Brad,
>
> You don't tell us if your MySQL is 32 bit?
>
> Stephan
>
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> h
It looks like eveything is there. This configuration looks almost identical
to my 32os machine.
root@brads-linux-laptop:/usr/lib# ldd libopendbx.so.1.2.0
linux-gate.so.1 => (0xf76df000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76b8000)
libc.so.6 => /lib/i386-lin
I've used the instructions defined on the "http://dbxtalk.smallworks.eu/";
website to setup the OpenDBXDriver for a MySQL database. When I try to make
a connection to the database, I'm getting the "function unavailable".
I have this working on a Ubuntu 14.04 32bit OS. I'm wondering if my prob
Esteban and Guille,
I just realized that you gentlemen are the keepers of DBXTalk. Thank you
for kindly corresponding with me. My hat's off to all of you for taking on
this task.
I have a somewhat grandeur goal for solving this problem. I would like to
solve the problem rather than creating a
I've contacted the OpenDBX development group and they seem to be unwilling to
add the "UNKNOWN" types to their library. So, that leaves us with solving
the problem in the GLORP framework.
The big problem is the GlorpOpenDbxDriver is asking the DBXRow for its value
- not rawValue, thereby trigger
Yes, the column type definition is: timestamp.
I am trying to use Pharo to access some old legacy MySQL tables. These
tables have "timestamps" defined everywhere and there is NO WAY I will be
allowed to change them. So, I'm going to have to try to figure out how to
get around this problem.
Si
Thank you for responding so quickly. The column in the database is defined as
a time stamp. It seems as though OpenDBX doesn't understand that type. I'll
try setting up date, date time, time, and timestamp columns and see what
happens.
-
Brad Selfridge
--
View this message in context:
http
Whenever I try to select a table that has timestamp defined columns I'm
getting the following error:
"OpenDBXDriverError: OpenDBXDriver: Unsupported data type: UNKNOWN, trying
to parse 2011-03-31 17:38:35"
I've traced this down into the NBOpenDBX_ApiH>>odbx_column_type:pos: method.
I don't know
12 matches
Mail list logo
